Steps to Configure the ASP.NET SAML 2.0 Module
Step 1: Pre-requisites: Download and Installation
-
Download
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:
https://<your-application-base-url>/?ssoaction=config
-
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
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.
Step 4: Testing SAML SSO
- Before testing, please ensure the following:
-
The ASP.NET (SP) SAML metadata has been exported to the identity
provider (IDP).
-
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:
-
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.
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
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
Step 6: Add the following link into your application for Single Sign-On
(SSO)
- 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>
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
perform SLO:
https://base-url/ssoaction=logout
-
For example, you can use it as:
<a href=”https://base-url/ssoaction=logout”>Log
out</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.
Secure your ASP.NET MVC applications by performing Single Sign-On (SSO) into
them. The miniOrange ASP.NET SAML 2.0 Connector supports C# and Visual Basic
languages. We also have modules for integrating 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.
Additional Resources:
Need Help?
Not able to find your identity provider? Mail us on
aspnetsupport@xecurify.com
and we'll help you set up SSO with your IDP and for quick guidance (via
email/meeting) on your requirement and our team will help you to select the
best suitable solution/plan as per your requirement.