ASP.NET OAuth Single Sign-On (SSO) Using Identityserver4 As OAuth Provider
ASP.NET OAuth Single Sign-On (SSO) module gives the ability to enable OAuth
Single Sign-On for your ASP.NET applications. Using Single Sign-On you can use
only one password to access your ASP.NET application and services. Our module
is compatible with all the OAuth compliant Identity providers. Here we will go
through a step-by-step guide to configure Single Sign-On (SSO) between ASP.NET
and IdentityServer4 as OAuth Provider.
For Setting up the connector, extract the
asp-net-oauth-sso-module.zip, you will find a DLL file
miniorange-oauth-sso.dll, a configuration file
oauthsso.config and a integration.md file which contain the
steps for adding the module into your application.
1. Add the connector in your application
Add miniorange-oauth-sso.dll in bin folder (where your other DLL
files exists) for your application.
Register miniorangeoauthsso module in your application according to
the provided steps in the integration.md file.
Add the provided configuration file oauthsso.config in the root
directory for your application.
After integration open browser and browse the connector dashboard with URL
below: https:// <your-application-base-url>/?ssoaction=config
If it pop up the registration page or login page, you have successfully
added the miniOrange oauth sso connector for your application.
Register or Login for configuring the connector.
2. Setup IdentityServer4 as OAuth Provider
Set up IdentityServer4 using guidelines provided
From Configure OAuth tab in Oauth Client plugin, collect Redirect/Callback
URL and enter it into your IdentityServer4.
Copy your Client ID and Client Secret and save it on your
miniOrange ASP.NET OAuth Client Configuration.
You have successfully completed your IdentityServer4 OAuth Server side
After configuring your OAuth Provider, it will provide you with
Client ID, Client Secret, Authorize Endpoint, Access Token Endpoint
and Get User Info Endpoint. Configure these values under respective
Fill all the required details and click on
4. Test Configuration
After saving configuration, click on the
Test Configuration button to verify if you have configured correctly.
On successful configuration, you will get
Attributes Name and Attribute Values on Test Configuration
window. The below screenshot shows a successful result.
5. Attribute Mapping
Map Attribute Names provided by your OAuth Server with your ASP.NET
application Attributes given under Attribute Mapping Section and click on
Save Attribute Mapping.
Note: All the mapped attributes will be stored in the session so that you
can access them in your application.
6. Integration Code
You can find the integration code in Integration Code tab in the
connector. Just copy-paste that code snippet wherever you want to access the
7. Add following link in your application for Single Sign-On (SSO)
Use the following URL as a link in your application from where you want to
perform SSO: http://base-url/?ssoaction=login
For example you can use it as: <a href="http://base-url/?ssoaction=login”>Log in</a>"
You can configure the ASP.NET SAML 2.0 Single Sign-On (SSO) module with any
Identity Provider such as
ADFS, Azure AD, Bitium, Centrify, G Suite, JBoss Keycloak, Okta,
OneLogin, Salesforce, AWS Cognito, OpenAM, Oracle, PingFederate, PingOne,
RSA SecureID, Shibboleth-2, Shibboleth-3, SimpleSAML, WSO2 or even with
your own custom identity provider.
If you dont hear from us within 24 hours, please feel free to send a follow up email to firstname.lastname@example.org
This privacy statement applies to miniorange websites describing how we handle the personal
When you visit any website, it may store or retrieve the information on your browser, mostly in the
form of the cookies. This information might be about you, your preferences or your device and is
mostly used to make the site work as you expect it to. The information does not directly identify
you, but it can give you a more personalized web experience.
Click on the category headings to check how we handle the cookies.
Strictly Necessary Cookies
Necessary cookies help make a website fully usable by enabling the basic functions like site
navigation, logging in, filling forms, etc. The cookies used for the functionality do not store any
personal identifiable information. However, some parts of the website will not work properly without
These cookies only collect aggregated information about the traffic of the website including -
visitors, sources, page clicks and views, etc. This allows us to know more about our most and least
popular pages along with users' interaction on the actionable elements and hence letting us improve
the performance of our website as well as our services.