We are trying out the integration of Adobe Target via Adobe DTM. The
situation is that there are some existing pages that already have mbox
integrated in the page. Now,when we rollout the Adobe Target tool via
Adobe DTM. We find that this tool is loading in every single page!. I
tried setting up the page specific criteria to identify the set of pages
where this needs to load. Though the mbox wrapper fires only on these
specific pages, the Mbox.js itself is still getting loaded in every
Thanks Sham, I did some progress... The things that I noticed that are
unusual for AEM 6.0 are a) actually, the SSOAuthenticationHandler looks
like a 2 in 1 🙂 IT does spin up a SSOLoginModule with a higher
ranking... when I see the JAAS section in Felix console, this is present
at a higher priority and it must be setting up the pre-auth login
credentials... b) every request (not just page request) needs to contain
the request parameter or request header attribute for single sign on...
the AEM s...
Thanks Sham! for you very quick response!! Pre-Auth Looks interesting...
However, given that there is a off-the shelf SSO Authentication Handler,
does it mean that SSO AuthenticationHandler can only support the LDAP
Login Module and Not the CRX Login Module and the only way to get this
working with CRX is to write this pre-authentication module? From what I
see in the AEM documentation -
is pretty cryptic Configure ...
Team, I just validating via POC where in , I should be able to do a
single sign on with just JCR OAK / CRX login Module. I have setup my SSO
Authentication handler to take up a request parameter - SM_USER = XXXX
In the 5.6.1 , the repository.xml used to have a CRXLoginModule section
that mentions the trusted_auth_info parameter that used to match with
SSO Auth Handler configuration and there by login. However, in 6.0 I see
the documentation (