Since there is no way to define which handler on the same path to trigger for authentication you would have to do some customization. You could implement a custom servlet /bin/auth and configure the authentication handlers under subpaths of the servlet - for example /bin/auth/saml.  When the user ac...

Here is the correct doc for 6.5:https://docs.adobe.com/content/help/en/experience-manager-65/administering/security/saml-2-0-authenticationhandler.html Sorry for the confusion with the 6.3 doc, I will notify our docs team.

AEM's SAML handler doesn't parse out the CN from the DN. However, you can just use the DN in AEM and it doesn't have to be visible to users. You can create the groups in AEM with the DN as the id, for example, "CN=APP-CRM-BUILD-PROFILE-CSR,OU=Resources,OU=_Groups,DC=lan,DC=xxxx,DC=org", then just gi...

You must configure the IDP to send the value you want.  This isn't handled by AEM.  In the AEM SAML Handler OSGi configuration, you would just set the "Group Membership" property with the name of the SAML attribute containing the list of the user's memberships (containing the group CNs instead of DN...

1. See the Single Page Application (SPA) feature set for AEM, here is the React tutorial:https://helpx.adobe.com/experience-manager/kt/sites/using/getting-started-spa-wknd-tutorial-develop/react/chapter-1.html If that is too tightly integrated then see the headless CMS features of AEM:https://docs.a...

Hi @sarakellyn  the official channel for pricing is here:https://www.adobe.com/products/request-consultation/marketing-cloud.htmlPlease fill out the form or call the number there and somebody would assist you.

I wrote a small app recently that does this so I could debug a product issue with content-sync.  You can download it here:https://documentcloud.adobe.com/link/track?uri=urn%3Aaaid%3Ascds%3AUS%3A52ae18bd-a1c4-48e6-b63f-25e31019bc6b The app is under /apps/test/test.jspYou run it by going to /apps/test...

Your maven pom.xml file for bundle IA_Wrapper_Services.core has the dependency for org.sling.apache.event set with the wrong version (mismatch to 6.5 version).  Please match your dependency version config for org.apache.sling.event in the pom.xml to match the bundle in /system/console/bundles.

If ResourceOnly flushes don't solve this then you can look into implementing a custom invalidation handler script:https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html#using-custom-invalidation-scriptshttps://arborydigital.com/blog/2019/...

Depending on the AEM version, you might also be hitting a product issue where response headers are reset on serving of asset files. To address that, you can apply the latest service pack - test locally to confirm.