Redirection from one module to another module is working in publish environment but if we check in domains it's asking for login everytime in each domain but is not happening in publish instance.
Views
Replies
Total Likes
Hi @deepankar2 ,
Are you trying to redirect from one domain to another domain within dispatcher?
would it be possible for you to share more details on the module (are they two different websites within AEM dispatcher)?
@konstantyn_diachenko @Shiv_Prakash_Patel @abhishekanand_ @A_H_M_Imrul @Madhur-Madan @BhavaniBharani @ChitraMadan @Dinesh_A @AdityaSuratwala If you're available, please check out this question and share your thoughts. Your help means a lot!
Views
Replies
Total Likes
would need more details, can you please provide the exact issue with some more details @deepankar2
Hi @abhishekanand_ ,
We got a requirement for SSO login functionality.
what we have done is we set token in cookie for both module and is working fine in publish environments as there was only one domain that is out publish domain.
But when we push this to our higher environment there are two different domains and just because of different domains we are not able to use the cookies, and is asking for login.
What we need to do for this case?
Thanks,
Deepankar
Views
Replies
Total Likes
@deepankar2 If you are having 2 no of publishers with different domains and if you are expecting token to work without asking login then you need to use encapsulated token support. Please find below article for stateless authentication using crypto.
https://experienceleague.adobe.com/en/docs/experience-manager-65/content/security/encapsulated-token
Note: If you change crypto keys then your keystore, SAML SSO will fail and you need to re create the keystore again.
Thanks
Ramesh
Hi @deepankar2,
although technically possible it's not a good practice to use cookies across domains. The recommended approach for SSO across different domains is to use an external authentication provider:
Good luck,
Daniel