Persistent browser session issues with Chrome

Question

Hi everyone

I have 2 Enterprise apps with SSO installed and to prevent MFA trigger everytime a user logs on I have enabled Persistent browser session.
I want MFA to sustain a higher level of security.

Now in Edge there is no problem. Persistent browser session works fine there. The users gets a one time MFA challenge and then can work on his/her session the next day when he or she logs on.
Only the Chrome user has to verify MFA every time he/she logs on.

I've enabled third party cookies.
Whitelisted all the Azure pages including: https://autologon.microsoftazuread-sso.com
Roaming profile and user policy Chrome.
Installed the Windows 10 user account extension: https://chrome.google.com/webstore/detail/windows-10-accounts/ppnbnpeolgkicgegkbkbjmhlideopiji

I've seem to run out of options. Am i overlooking someting in the profile of the user that's resetting a session state?
Chrome does know my idenity, but doesn't know that I have an open session.

Many thanks for your help.

Kind regards,

Andre

Answer 1

It looks like you have tried a number of steps to resolve this issue with Chrome not maintaining a persistent browser session.

Have you tried clearing the browser cache and cookies to see if that resolves the issue? Another suggestion would be to see if there are any browser extensions that may be conflicting with the persistent session and disabling them to see if that resolves the issue.

It may also be helpful to check the browser settings to see if there is an option to maintain persistent sessions or keep the browser logged in.

Lastly, it may be worth reaching out to the support team of the enterprise apps that you are using with SSO to see if they have any specific suggestions or troubleshooting steps to resolve the issue.

Answer 2

@BIJUMON @Khurram Rahim It places cookies with session state so you want to keep them.

In my case the Azure Hybrid Join is works fine. Because it trust the device (Conditional Access) it logs you on even in Chrome.

Or another solution

I've researched it and tested it, it is a while a go. What you need to do is allow third party cookies and cookies. Play with it a little, you can add url's too. I've researched it and that worked for machines who had less strict policies.

Answer 3

the same here... any solution?