Keycloak and SSO in ASP.NET MVC 5 (edit)

Keycloak and SSO in ASP.NET Core

An example single page core application that uses Angular and Keycloak as identity provider.


Keycloak - Server Application Guide

Xác thực tiếng Việt


Hi nageshrgosul,

According to your description, as far as I know, you want to implement cross domain SSO,

Single Sign On (SSO) for cross-domain ASP.NET applications: Part-I - The design blue print: 

Single Sign On (SSO) for cross-domain ASP.NET applications: Part-II - The implementation: 

Introducing Single Sign-on to an existing ASP.NET MVC application: 

Best Regards,

Eric Du

SSO in .NET Core

  • AspNet.Security.OpenIdConnect.Server (ASOS)
  • Gluu Server
  • IdentityServer
  • OpenIddict

IdentityServer4 is an OpenID Connect and OAuth 2.0 framework for ASP.NET Core. IdentityServer4 enables the following security features:

  • Authentication as a Service (AaaS)
  • Single sign-on/off (SSO) over multiple application types
  • Access control for APIs
  • Federation Gateway

SSO: (Show Code) (Show Code) (Chargeable)


There are multiple options to implement SSO for a .NET application.

Check out the following tutorials online:

Basics of Single Sign on, July 2012

GaryMcAllisterOnline: ASP.NET MVC 4, ADFS 2.0 and 3rd party STS integration (IdentityServer2), Jan 2013

The first one uses ASP.NET Web Forms, while the second one uses ASP.NET MVC4.

If your requirements allow you to use a third-party solution, also consider OpenID. There's an open source library called DotNetOpenAuth.

For further information, read MSDN blog post Integrate OpenAuth/OpenID with your existing ASP.NET application using Universal Providers.

Hope this helps!


Single Sign On (SSO) for cross-domain ASP.NET applications: Part-II - The implementation

Original source ccan be located at

Al-Farooque Shubho, 4 Oct 2010

Implementation approach of a domain independent Single Sign On (SSO) for ASP.NET applications.


SSO in Microsoft:

Authorized client applications section, you identify the applications that you want to authorize to your add-in's web application. Each of the following IDs needs to be pre-authorized.

  • d3590ed6-52b3-4102-aeff-aad2292ab01c (Microsoft Office)
  • ea5a67f6-b6f3-4338-b240-c655ddc3cc8e (Microsoft Office)
  • 57fb890c-0dab-4253-a5e0-7188c88b2bb4 (Office on the web)
  • 08e18876-6177-487e-b8b5-cf950c1e598c (Office on the web)
  • bc59ab01-8403-45c6-8796-ac3ef710b3e3 (Outlook on the web)