Restart is a must get it work. I also configured and it worked only after restart,

Tuhin Ghosh wrote... By settings I meant configuration in the config manager. sorry for the confusion. Actually when I was doing a POC with SAML I also faced this infinite loop issue, but then adding everyone and content-authors in the default group solved the infinite loop issue for me. If that is ...

Also observed that everytime it loop in, it creates a new user token. I checked in tokenmagr and it keep adding new user token as we loop in. But if we stop the loop and then hit the URL then it repects that user. So to conclude, somehow the SAML and AEM login service are not coordinating properly.

Tuhin Ghosh wrote... Hi Ravi,   Yes, thats how the SAML should work, its not necessary to have the user present in the crx. Just wondering if you have tested adding the content-authors group in the settings and check once.   Thanks Tuhin Hi Tuhin, What do you mean by adding in settings? I have added...

Tuhin Ghosh wrote... Hi Ravi,   I guess you have not removed the everyone group. both 'everyone' and 'content-authors' are there, correct?   Thanks Tuhin  Hi Tuhin,I had both groups in the default list but still it didnt worked. 

Tuhin Ghosh wrote... kindly try adding content -author group and see if that solves the issue. The ootb saml integration sometime wants an additional group other than everyone. If that works you could change it to more meaningful custom group later.  Hi Tuhin,I updated the default group to be conten...

No. The user does not have admin privilege. The flow is that the saml gives the user data only; at that point of time he does not belong to any group. I have added in SAML config the default group to be everyone. Hence once the user logs in he will then be marked to default everyone group.

I will add and will check the outcome.

I have added everyone group already but still the same issue. Its done at the publisher so not sure if we have to add content-author group.

Dear All,I have integrated SAML on publisher and it works fine in few scenarios. But when the page is cached and If we try to access the same page from a different browser, it gives me a popup saying the session is expired and it then request to login via our SAML login page which is expected. But t...