{"id":62308,"date":"2024-07-31T22:40:50","date_gmt":"2024-07-31T17:10:50","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=62308"},"modified":"2024-07-31T23:55:10","modified_gmt":"2024-07-31T18:25:10","slug":"aem-saml-integration-step-by-step-guide","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/aem-saml-integration-step-by-step-guide\/","title":{"rendered":"AEM SAML Integration \u2013 Step by Step Guide"},"content":{"rendered":"

In the dynamic landscape of digital experience management, security and user convenience are paramount. Adobe Experience Manager (AEM) stands out as a leading solution, empowering organizations to create, manage, and deliver engaging digital experiences. However, with the increasing importance of security, integrating robust authentication mechanisms like Security Assertion Markup Language (SAML) with Single Sign-On (SSO) capabilities becomes essential. In this blog post, we’ll delve into the world of AEM SAML integration, unraveling the complexities of SSO and authentication to streamline user experiences while fortifying digital defenses.<\/span><\/p>\n

We will be using the SP initiative for authentication in our case. Below is the diagram to help understand the authentication process:<\/span><\/p>\n

\"AEM

AEM SAML Authentication Flow<\/p><\/div>\n


\n<\/span>Configuration of Identity Provider (IdP)<\/strong><\/span><\/p>\n

    \n
  1. Register for Okta trial account<\/span><\/li>\n
  2. Navigate to Admin dashboard<\/span><\/li>\n
  3. Navigate to Application \u279d Create App Integration<\/span><\/li>\n
  4. Choose SAML 2.0<\/span><\/li>\n
  5. Add Application Configs:<\/span>\n
    \"Application

    Application Config<\/p><\/div>\n

    \"Profile

    Profile Attributes<\/p><\/div>\n

      \n
    • Single Sign-on URL<\/b> – An authentication request from AEM to Okta first goes to<\/span> https:\/\/<domain>\/<\/span><Service Provider Entity ID>\/saml_login<\/span><\/li>\n
    • Service Provider Entity ID<\/b> – Identifier for Service provider, same to be defined in SAML Authentication Handler)<\/span><\/li>\n
    • Signature Certificate<\/b> – Locally generated certificate<\/span><\/li>\n
    • Single Logout UR<\/b>L – URL to redirect to while logging out<\/span><\/li>\n
    • Attribute Statements<\/b> – add attributes to sync value with AEM like uid \u2192 user.login etc<\/span><\/li>\n
    • Group Attributes <\/b>– attribute to add a user to the desired group in AEM<\/span><\/li>\n<\/ul>\n<\/li>\n
    • Create the desired groups in Okta and assign the relevant users to it<\/span><\/li>\n
    • Add relevant users to your app<\/span><\/li>\n
    • Once the setup is complete, navigate to <\/span>Sign On,<\/b> and on the right rail click on <\/span>View SAML Setup Instructions<\/b> and save the following:<\/span>\n
        \n
      • Identity Provider Single Sign-On URL<\/span><\/li>\n
      • Identity Provider Single Logout URL<\/span><\/li>\n
      • Certificate<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n

        Configuration of Service Provider (SP)<\/strong><\/span><\/p>\n

          \n
        1. Map a demo hostname for localhost<\/span><\/li>\n
        2. Generate local certificate and private key<\/span>\n
            \n
          • Generate a private key using OpenSSL<\/span><\/li>\n
          • Create a CSR<\/span><\/li>\n
          • Generate local certificate using private key and CSR<\/span><\/li>\n
          • Convert private key to DER format\u00a0<\/span><\/li>\n<\/ul>\n<\/li>\n
          • Add locally generated certificate and private key to <\/span>authentication-service<\/b> user\u2019s Keystore<\/span><\/li>\n
          • Add Okta certificate to AEM Trust Store and get Okta alias<\/span><\/li>\n
          • Navigate to the AEM config manager open <\/span>Adobe Granite SAML 2.0 Authentication Handler <\/b>and<\/span> update the following fields:<\/span>\n
              \n
            • Path<\/b> – Root path that is to be authenticated\u00a0<\/span><\/li>\n
            • IDP URL<\/b> – URL where authentication request is sent to (embed URL from okta config)<\/span><\/li>\n
            • IDP Certificate alias<\/b> – Alias received from Trust Store<\/span><\/li>\n
            • Service Provider Entity ID<\/b> – Identification ID for the SP (Should match the SP Entity ID from okta config)<\/span><\/li>\n
            • SP private key alias<\/b> – authentication-service keystore alias<\/span><\/li>\n
            • Key Store Password <\/b>– authentication-service keystore alias<\/span><\/li>\n
            • User ID attribute<\/b> – Unique identified for our user coming from Okta<\/span><\/li>\n
            • Use Encryption<\/b> – Whether or not to encrypt SAML messages<\/span><\/li>\n
            • Auto-create CRX users<\/b> – Whether we want new users to be created (ones coming from Okta)<\/span><\/li>\n
            • Add to groups<\/b> – Whether we want to add the incoming users to groups mentioned in the group-membership field<\/span><\/li>\n
            • Group Membership<\/b> – Attribute in the SAML response that mentions the user’s group name<\/span><\/li>\n
            • Default Group<\/b> – Default group for users to be added to. It does not pick a value from the SAML response<\/span><\/li>\n
            • Synchronized Attributes<\/b> – key-value pair which represents (attribute coming from SAML request)=(relative location to user’s profile node in CRX where we want to save the property). Ex. email=profile\/email<\/span><\/li>\n
            • Handle Logout<\/b> – Whether we want the ability for users to logout<\/span><\/li>\n
            • Logout URL<\/b> – IDP URL to hit to remove logged-in user session<\/span><\/span><\/span>\n
              \n
                \"SAMLSAML Config Image<\/ul>\n<\/div>\n

                \"SAML

                SAML Config Image<\/p><\/div><\/li>\n<\/ul>\n<\/li>\n

              • Open the <\/span>Apache Sling Logging Logger Configuration<\/b> and update the following fields (Custom SAML logging):<\/span>\n
                  \n
                • Log Level: Debug<\/span><\/li>\n
                • Log File: logs\/saml.log<\/span><\/li>\n
                • Logger: com.adobe.granite.auth.saml<\/span><\/li>\n<\/ul>\n<\/li>\n
                • Open the <\/span>Apache Sling Referrer Filter<\/b> and update the following fields (Allow SP and IDP referrer endpoints):<\/span>\n
                    \n
                  • Allow empty – true<\/span><\/li>\n
                  • Allow Hosts – Allow IDP(Okta) origin URL<\/span><\/li>\n
                  • Allow Regexp Host – Allow SP domain<\/span><\/li>\n<\/ul>\n<\/li>\n
                  • Open the <\/span>Apache Sling Authentication Service<\/b> and update the following fields:<\/span>\n
                      \n
                    • Authentication Requirements – Add SP domain prefix-ed by a ‘+’<\/span><\/span>\n

                      \"AEM

                      Authentication Service Config Image<\/p><\/div><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n

                      Conclusion:<\/b><\/span><\/p>\n

                      In conclusion, AEM SAML integration with SSO capabilities represents a significant advancement in enhancing both security and user experience within digital experience management. By leveraging SAML’s authentication mechanisms, organizations can fortify their AEM instances against potential threats while providing users with a frictionless authentication experience.\u00a0 With the above steps, you can integrate SAML authentication capability into your website and enhance user experience significantly.\u00a0<\/span><\/p>\n

                      If you still have questions, comment and join the discussion! Meanwhile, follow us on social media for more updates.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                      In the dynamic landscape of digital experience management, security and user convenience are paramount. Adobe Experience Manager (AEM) stands out as a leading solution, empowering organizations to create, manage, and deliver engaging digital experiences. However, with the increasing importance of security, integrating robust authentication mechanisms like Security Assertion Markup Language (SAML) with Single Sign-On (SSO) […]<\/p>\n","protected":false},"author":1762,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":1420},"categories":[5868],"tags":[4847,1221,2895],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/62308"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/1762"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=62308"}],"version-history":[{"count":14,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/62308\/revisions"}],"predecessor-version":[{"id":63698,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/62308\/revisions\/63698"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=62308"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=62308"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=62308"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}