We are using mixed mode auth using Okta for Optimizely editors and Azure B2C for end users. Right now we share the same cookie auth scheme (to be able to keep the Optimizely Quick Navigator).
We have set cookie expiration. We noticed that Optimizely UI (edit/admin) does not handle cookie expiration that very gracefully. Api endpoints fails and unexpected errors just pops up in the notification area. Not the best editor experience. Editor can reload (rechallange on the idp) and everything is fine until next expiry.
Didn't Optimizely UI have auto-logout prompt at some point? So if the editor leaves for lunch we will have the prompty on the screen when he comes back (and the cookie has expired)?
Are we taking the wrong approach? (short expiration is a customer security requirement)
Did you find an answer to this?We are in the same kind of situatuion.
Hi Palle and Felicia
I once had similar errors in a setup with Azure AD, where the editor authentication would expire after some idle time.
The issue was that API requests would be redirected to the login page (with 302 Found), which was not taken well by the editor UI. So I changed it to return 401 for editor API requests. If you set up the integration according to the CMS 12 documentation, this should already be handled.
Do you have custom handlers in the OnRedirectToIdentityProvider event handler that overrides the 401 status code?