Hi Tony,
In order to replace built-in local login with Azure AD follow official documentation: Integrate Azure AD using OpenID Connect (optimizely.com).
I don't have an expirenece with WS-Federation but this article describes how to add it in .Net Core project: Authenticate users with WS-Federation in ASP.NET Core | Microsoft Learn
Be sure to also follow Vincent 2nd point and at the end you must manually synchronize user roles with Optimizely using: await synchronizingUserService.SynchronizeAsync(claimsIdentity);
Thanks. Well I got configuration from IT services now and I was directed to use SAML2 instead, so I am devicing a configuration for that, but that page contains some new info.
I switched to SAML2 instead, and moved the configuration to progam.cs instead of startup.cs. For some to me unknown reason the same configuration refused to work under startup.cs, but worked fine in program.cs. Maybe a timing issue.
/ Tony
Hi,
I am trying to set up a federated login scheme against AD in CMS12, .NET Core 8 using cookies, but I it redirects to the default yellow/white login screen /Util/Login?ReturnUrl=%2F both locally and on integration environment instead of redirecting to MetadataAddress. Before we ran OWIN but, now we are upgrading to latest CMS 12.
What I have done:
In appsettings:
{
"EPiServer": {
"Login": {
"Wtrealm": "https://our.address",
"MetadataAddress": "https://our.address/federationmetadata/2007-06/federationmetadata.xml"
}
}
}
Has anyone had this behavior before? I am thinking I missed something easy :S
/ Tony