AEM SAML Authentication not working on new site | Community
Skip to main content
saibul
saibul
Level 4
December 31, 2020
Question

AEM SAML Authentication not working on new site

  • December 31, 2020
  • 3 replies
  • 2330 views


We created a new site and configured the SAML in configMgr.

The path of the new site is "/content/site2/us/en/voice". The new site path and serviceProviderEntityId are added to the new SAML config.
We don't want to configure "Authentication Requirement" or "Closed User Group" in the new site properties path as we want all the AD users should access the new site.
In the new site when hit the URL it just renders the page instead of redirecting to idp.

 

 

SAML integration with AzureAD is working in the existing site.
Also in the existing site page properties I didn't see any "Authentication Requirement" or "Closed User Group" configured.
when we hit the existing site URL it automatically redirects to AD and shows the AD login screen, once passed the credentials it redirects the page based on the redirectURL configured in AD.


Am I missing anything? Advance thanks for your answers & recommendations.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

saibul
saibulAuthor
Level 4
December 31, 2020
Also there is no logs captured. I configured the log for com.adobe.granite.auth.saml package as well.
Pawan-Gupta
Pawan-Gupta
Level 8
December 31, 2020

Hello,

 

Did you configure your next site under same domain or using separate domain??

 

Thanks,

Pawan

    saibul
    saibulAuthor
    Level 4
    January 1, 2021

    same subdomain. moving forward it will be a new subdomain.

     

    Even I replace the new site path in the existing site SAML2.0 Authentication Handler config. Still no luck

    saibul
    saibulAuthor
    Level 4
    January 1, 2021

    Also found in the below blog that this is the default behavior of publish and we need to add the path in (org.apache.sling.engine.impl.auth.SlingAuthenticator.xml) config

    https://www.bounteous.com/insights/2018/09/24/single-sign-sso-integration-okta-aem-63/#troubleshooting

     

    When I check my SlingAuthenticator.xml there is no existing site path entry in the config. 

     

     

    Terms & ConditionsAccessibility statement

    Loading footer...