Enable IP Allow List Support for Content Hub Delivery Endpoints - Status changed to: Investigating

[#1]

Request for Feature Enhancement (RFE) Summary:	Based on the customer’s internal IT policy, it is required to restrict access to Content Hub endpoints using an IP allow list, similar to the current IP-based access control available for AEM Author (DAM). Without this capability, there is a significant risk that the customer will be unable to adopt Content Hub in their production environment due to internal security compliance requirements.
Use-case:	The customer utilizes AEM Assets and Content Hub to share content with both internal teams and external agency users. For security and compliance reasons, access to internal content must be restricted to pre-approved IP addresses. While AEM Author supports IP allow list configurations, Content Hub delivery endpoints are currently publicly accessible and do not support the same level of access control. The customer requires the ability to limit access to Content Hub by IP to align with internal security policies.
Current/Experienced Behavior:	Content Hub delivery endpoints (e.g., *-delivery) are publicly accessible by default. There is no configuration available to apply IP allow list restrictions specifically for Content Hub. IP restrictions set on AEM Author do not apply to Content Hub endpoints.
Improved/Expected Behavior:	Content Hub should support IP allow list functionality, allowing administrators to define which IP ranges are permitted to access delivery endpoints. If a user attempts to access Content Hub from a non-approved IP, the system should block access and return a 403 error. Ideally, this feature would also allow for different IP configurations for internal users and external partners.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as a Cloud Service
Screenshot (if applicable):
Code package (if applicable):

[#2]

@UnjiBa Thanks for proposing this idea. This has been reported to the engineering under the internal reference ASSETS-56551. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to Jira's status.