SaaS CMS has officially launched! Learn more now.

Azure AD integration with Optimizely webforms ( version 9.9)

Vote:
 

We have our application running on ASP.NET web form with Optimizely 9.9. We would like to integrate our solution with AZURE AD. Can someone please suggest whether this is possible with Optimizely v9.9.1 and asp.net web form. and If not , what is the pre-requsite required for integration.

#324903
Jul 04, 2024 10:29
Vote:
 

Hi Vishal

This is possible and well documented.

However, the names and versions have changed in the documentation. For instance, the documentation mentions Entra ID, which is the new name for Azure AD. And it mentions CMS 11, but CMS 9 is basically the same in this regard.

You can use the sample code pretty much as-is. But be prepared for some things to work differently. One thing, consider using the Authorization Code flow, instead of the implicit flow. That will be safer. I would also keep ValidateIssuer at default, instead of false.

#325023
Jul 07, 2024 11:44
Vote:
 

Hi Stefan,

Thank you for the response. 1 more question: Will we be able to integrate AZURE AD with our asp.net web form based application. O was going through the documentation that you shared, and it expects configuratio code to be written in startup class. As ours in ASP.NET web form application, I dont think we can have startup call as startup class was introduced in MVC and .NET core.

Can you please suggest how we can integrated the code in web form.

#325062
Jul 08, 2024 8:08
Vote:
 

The startup class is an OWIN feature, not a Web Forms feature. And, as I recall it, CMS 9 is technically a mix of MVC and Web Forms.

So you can introduce OWIN, with OpenID Connect. But you will then be turning off Forms Authentication. Meaning, you can not use mixed-mode authentication (where customers log in using username/password), unless you migrate Forms Authentication to ASP.Net Identity. But maybe you don't have such requirements.

You will just do as documented. Whenever the CMS requires authentication, it will invoke the OWIN authentication instead of the Forms Authentication.

And for the LogoutPath, in the documentation, use /Util/Logout.aspx, instead of /logout.

#325063
Jul 08, 2024 8:14
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.