Skip to main content
Aditya3343
April 26, 2023
Solved

Adobe Experience Manager Author Instance integration with Azure AD with SAML 2.0

Hi Team,

I have configured my local AEM set up with SAML 2.0 OOTB authentication handler and I am able to authenticate user.

 

While It is coming to Group Assignment, I have created Local AEM group with same name as Azure AD Security Group.

But user is not getting assigned to this group though it is getting added to default groups specified in SAMl Authentication handler.

 

Few Configurations:

Autocreate CRX Users : True

Add to Groups : True

Group Membership: http://schemas.microsoft.com/ws/2008/06/identity/claims/groups

NameIdPolicy Format: urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

Synchronized Attributes: http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress=profile/email

                                       http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname=profile/givenName 

                                       http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname=profile/familyName 

 

What I am missing here?

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
rawvarun
rawvarunAccepted solution
Community Advisor
May 30, 2023

You can set up a Logger to debug any issues arising from misconfiguring SAML. You can do this by:

  1. Going to the Web Console at http://localhost:4502/system/console/configMgr

  2. Search for and click on the entry called Apache Sling Logging Logger Configuration

  3. Create a logger with the following configuration:

    • Log Level: Debug
    • Log File: logs/saml.log
    • Logger: com.adobe.granite.auth.saml
Varun Rawat
View in thread

2 replies

Shashi_Mulugu
Community Advisor and User Group Leader
Shashi_MuluguCommunity Advisor and User Group Leader
Community Advisor and User Group Leader
May 8, 2023

@aditya3343 groupmembership is the field which should get the group name from assertion response from SAML.. so make sure of that.

Translate
    rawvarun
    Community Advisor
    rawvarunCommunity AdvisorAccepted solution
    Community Advisor
    May 30, 2023

    You can set up a Logger to debug any issues arising from misconfiguring SAML. You can do this by:

    1. Going to the Web Console at http://localhost:4502/system/console/configMgr

    2. Search for and click on the entry called Apache Sling Logging Logger Configuration

    3. Create a logger with the following configuration:

      • Log Level: Debug
      • Log File: logs/saml.log
      • Logger: com.adobe.granite.auth.saml
    Translate
    Varun Rawat
      Terms & ConditionsAccessibility statement

      Loading footer...