For your WS-Fed scheme to actually trigger a login flow, something need to do challenge for that scheme. E.g. a 401 response. /util/login won't do that, since that view allows anonymous requests.
Why have you onfigured with a policy scheme? Do you intend to support multiple authentication schemes, i.e. "mixed mode"?
What happens if you configure default scheme and default challenge scheme to
WsFederationAuthenticationDefaults.CookieName? Then try to access /episerver/cms. Does the correct login flow happen?
We are in process of migrating to Optimizely 12 (.NET 6). In this connection I am having some issue migrating ADFS and to make it work as default authentication for Optimizely admin site login
I have followed this guideline from Optimizely -> https://docs.developers.optimizely.com/content-cloud/v12.0.0-content-cloud/docs/mixed-mode-authentication and also Microsoft recommendations on this area
Code from Startup.cs class
When I go to -> https://localhost:5001/util/login?ReturnUrl=%2fepiserver it just shows the normal login page and not our ADFS login page.
Any help would be appreciated