Configuring SAML security to allow Experience Manager in Chrome
To enable users to access Experience Manager on later versions of the Chrome browser, update the noHttpAuthenticationForUrls attribute in Content Manager's security settings to allow Experience Manager.
About this task
If you have implemented SAML authentication for Content Manager, users of Chrome version 80 and later may be blocked from accessing the Experience Manager user interface and Chrome may also show a Javascript error in its debug console.
Chrome 80 introduced a SameSite cookie classification, which blocks any cookies that are not labeled in a certain way. After this update, Chrome no longer classifies Experience Manager as safe. As a workaround, we recommend that you follow this procedure to configure Content Manager security so that SAML will not authenticate the Experience Manager URLs that allow editing content.