ASP.NET SAML Single Sign-On (SSO) module gives the ability to enable SAML 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 SAML compliant identity providers. Here we will go through a step-by-step guide to configure Single Sign-On (SSO) between ASP.NET and Auth0 considering Auth0 as IdP. To know more about the other features we provide, click here.

Download And Extract Package

• Download miniOrange ASP.NET SAML 2.0 Module.
• For Setting up the module, extract the asp-net-saml-sso-module-xxx.zip, you will find a DLL file miniorange-saml-sso.dll, a configuration file saml.config and a integration.md file which contain the steps for adding the module into your application.

Steps to configure ASP.NET SAML Single Sign-On (SSO) using Auth0 as IDP

1. Add module on ASP.NET Application

• Add miniorange-saml-sso.dll into your bin folder (where other DLL files for your application exist).
• Register minorangesamlsso module in your application according to the steps provided in the file named integration.md.
• Add the provided configuration file saml.config in the root directory of your application.
• After integration open browser and browse the module dashboard with URL below:
https://<your-application-base-url>?ssoaction=config
• If it pops up the registration page or login page, you have successfully added the miniOrange saml sso module for your application.


• Register or login with your account by clicking the Register Button for configuring the module.

2. Configure Auth0 as Identity Provider

• You need to send your SP metadata to your identity provider, Auth0. For SP metadata, use the SP metadata URL or download the SP metadata as a .xml file and upload it at your IdP end. You can find both these options under the Service Provider Settings tab.

• Alternatively, you can manually add the SP Entity ID and ACS URL from Service Provider Settings tab in the plugin to your IdP configurations.

• Log in to your Auth0 dashboard.
• Click on Applications.

• Click on Create Application.

• A new window will pop-up. Enter a name for the application and select Regular Web App. Click on CREATE button.

• Select the Connection Tab and enable Username Password Authentication

• Select the Addons tab.

• Enable SAML2 option in the addons. It will open up a Configuration window.

• Enter Application Callback URL, Audience, Recipient and other settings using SP entity ID and ACS URL copied from the plugin as shown below:

• Scroll down and click on Save.

• Go to the Usage tab and click on the Identity Provider Metadata download link. It will download the metadata XML file which you'll need for setting up the SAML plugin.

• You have now successfully configured Auth0 as IDP

3. Configure ASP.NET SAML Module as Service Provider

Note: After installation of the plugin, we need to setup the trust between your ASP.NET application and Auth0. SAML metadata is shared with Auth0 so they can update their inbuilt configuration to support Single Sign-On.

2.1: Share SAML Metadata with Auth0

• Click on Add New IDP to configure ASP.NET Single Sign-On (SSO) with Auth0.

• Under Service Provider Settings tab, you can either copy-paste the metadata URL on your IDP side or download the SP metadata as an XML file. Additionally, you have the choice to manually copy and paste Base URL, SP Entity ID, and ACS URL.
• Share SAML metadata with your identity provider.

2.2: Import Auth0 SAML metadata

• Select Auth0 from the list of identity providers shown below.

There are two ways detailed below with which you can configure your SAML identity provider metadata in the module.

A] Upload metadata using the Upload IDP Metadata button:

• If your identity provider has provided you with the metadata URL or metadata file (.xml format only), then you can simply configure the identity provider metadata in the module using the Upload IDP Metadata option.
• You may refer to the screenshot below:

• You can choose any one of the options according to the metadata format you have available.

B] Configure the identity provider metadata manually:

• After configuring your identity provider, it will provide you with IDP Entity ID, IDP Single Sign On URL and SAML X509 Certificate fields respectively.
• Click Save to save your IDP details.

You have successfully configured your ASP.NET application as a service provider.

4. Testing SAML SSO

• Before testing, please ensure the following:
• The ASP.NET (SP) SAML metadata has been exported to Auth0 (IDP).
• Importing the Auth0 (IDP) SAML metadata in ASP.NET (SP).
• To test whether the SAML configuration you’ve done is correct, hover on Select Actions and click on Test Configuration.

• Note: In the trial version of the plugin, you can only configure and test one identity provider (IDP).
• The screenshot below shows a successful result. Click on Done to further continue with the SSO Integration.

• If you are experiencing any error on the module end you’ll be shown with the window similar to below.

• To troubleshoot the error you can follow the below steps:
• Under Troubleshooting tab, enable the toggle to receive the plugin logs.


• Once enabled, you will be able to retrieve plugin logs by navigating to Identity Provider Settings tab and clicking on Test Configuration.
• Download the log file from the Troubleshoot tab to see what went wrong.
• You can share the log file with us at aspnetsupport@xecurify.com and our team will reach out to you to resolve your issue.

5. Integration Code

• This step allows you to specify the sso prefix of the session or claims parameter that will be used to access user attributes in your application.
• If you're still confused about how the integration steps work, take a look at the Setup Tour.

• Select the mode for storing SSO attributes, and you will now see the integration code based on the authentication method you selected and the language your application uses.
• Just copy-paste that code snippet wherever you want to access the user attributes.

• Note: This trial module only supports session-based authentication and User Claims is available in the premium plugin.
• Note: All the mapped attributes will be stored in the session so that you can access them in your application.
• If you want some assistance regarding the integration code, get in touch with us at aspnetsupport@xecurify.com

6. Login Settings

• Hover on Select Actions and click on Copy SSO Link.

• Use the copied link in the application from where you want to perform SSO:
  https://base-url/?ssoaction=login
• For example, you can use it as:
  <a href=”https://base-url/?ssoaction=login”>Log in</a>

7. Logout Settings

• Use the following URL as a link in your application from where you want to perform SLO: https://<your-application-base-url>/?ssoaction=logout
• For example you can use it as: <a href="https://<your-application-base-url>/?ssoaction=logout">Logout</a>

You can even configure the DNN SAML 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. To check other identity providers, click here.

Additional Resources

• ASP.NET OAuth Single Sign-On (SSO)
• Web3 login for ASP.NET Applications
• DNN SAML Single Sign-On (SSO)
• DNN REST API Authentication
• nopCommerce SAML Single Sign-On (SSO)
• nopCommerce OAuth Single Sign-On (SSO)
• Umbraco SAML Single Sign-On (SSO)