Steps to Configure the ASP.NET SAML 2.0 Module
Note: We recommend to install this library in your ASP.NET web
but in case you do not have access to the application source code or you are
not a developer, you can proceed further with the
Manual installation steps.
Step 1: Pre-requisites: Download and Installation
miniOrange ASP.NET SAML 2.0 Module.
To set up the module, extract the file
asp.net-saml-sso-module-xxx.zip. You will find a DLL named
miniorange-saml-sso.dll, a configuration file named
saml.config and an integration.md file which contains
steps for adding the module into your 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 your browser and browse the connector dashboard
with the URL below:
If the registration page or login page pops up, you have successfully
added the miniOrange SAML SSO connector to your application.
Register or log in with your account by clicking the
Register button to configure the module.
Step 2: Configure your identity provider
You need to send your SP metadata to your identity provider. 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
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
Step 3: Configure ASP.NET as Service Provider (SAML SSO Module)
Note: After installation of the plugin, we need to setup the trust
between your ASP.NET application and your identity provider. SAML metadata
is shared with identity provider so they can update their inbuilt
configuration to support SAML Single Sign-On.
3.1: Share SAML Metadata with identity provider
Click on Add New IDP to configure ASP.NET SAML Single Sign-On (SSO)
using your identity provider.
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.
3.2: Import identity provider SAML metadata
- Select your identity provider from the list shown.
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
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.
Step 4: Testing SAML SSO
- Before testing, please ensure the following:
The ASP.NET (SP) SAML metadata has been exported to the identity
Importing the identity provider (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:
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
Download the log file from the Troubleshoot tab to see
what went wrong.
You can share the log file with us at
and our team will reach out to you to resolve your issue.
Step 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
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
Step 6: Add the following link into your application for SAML Single Sign-On
Hover on Select Actions and click on Copy SAML SSO Link.
Use the copied link in the application from where you want to perform SAML
For example, you can use it as:
Step 7: Add the following link into your application for SLO
Use the following URL as a link to your application from where you want to
For example, you can use it as:
You can configure the
ASP.NET 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. Secure your ASP.NET MVC applications by performing SAML Single Sign-On
(SSO) into them. The miniOrange ASP.NET SAML 2.0 Connector supports C# and
Visual Basic languages.
We also provide
DNN SAML Single Sign-On (SSO) Connector.
to know more.
miniOrange also has modules for integrating with legacy applications like
Active Directory, SiteMinder, Radius, Unix, and others. Using SAML,
OAuth, OpenID, ADFS, and WSFED protocols, we can help you add
login/authentication to your ASP.NET site.
Not able to find your identity provider? Mail us on
email@example.com and we'll help you set up SSO into ASP.NET with your custom IDP. For
quick guidance (via email/meeting) on your requirement, our team will help
you to select the best suitable solution/plan as per your requirement.