IP restriction for ingress integration via Service Credentials | Community
Skip to main content
M
msatsura
New Participant
November 23, 2022
Investigating

IP restriction for ingress integration via Service Credentials

  • November 23, 2022
  • 1 reply
  • 385 views
Request for Feature Enhancement (RFE) Summary:

Restrict IP access for ingress integration that use Service Credentials on AEMasCS author without putting the whole environment behind vpn
Use-case: The third-party connector leverages Service Credentials to access AEM as a cloud Author. It uses POST and Sling Post requests for updates in AEM. We want to make sure that if the credentials are compromised, nobody would be able to make any updates to the production environment from IPs that are not whitelisted. While the environment should be still publicly accessible.
Current/Experienced Behavior: No IP restrictions per Service Credentials/Integration
Improved/Expected Behavior: It is possible to restrict the access for the integrations per IP
Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service
Customer-name/Organization name: Macys
Screenshot (if applicable):  
Code package (if applicable):  

1 reply

kautuk_sahni
kautuk_sahni
Employee
January 11, 2023

@msatsura 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference CQ-4351178. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

Kautuk Sahni
Terms & ConditionsAccessibility statement

Loading footer...