Step 3: Configure your Identity Provider
-
Under the Plugin Settings tab, select your identity provider from
the list shown.
There are two ways detailed below with which you can get the SAML SP
metadata to configure onto your identity provider end.
A] Using SAML metadata URL or metadata file:
-
In the Plugin Settings menu, look for
Service Provider Settings. Under that, you can find the metadata
URL as well as the option to download the SAML metadata.
-
Copy metadata URL or download the metadata file to configure the same on
your identity provider end.
- You may refer to the screenshot below:
B] Uploading metadata manually:
-
From the Service Provider Settings section, you can manually copy
the service provider metadata like
SP Entity ID, ACS URL, Single Logout URL
and share it with your identity provider for configuration.
- You may refer to the screenshot below:
Step 4: Configure your Service Provider (SSO Module)
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.
Step 5: Test Configuration
-
Click on the Test Configuration button to test whether the SAML
Configuration you’ve done is correct.
-
The screenshot below shows a successful result. Click on
SSO Integration 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
Troubleshoot
tab, enable the toggle to receive the plugin logs.
-
Once enabled, you will be able to retrieve plugin logs by navigating
to Plugin 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 6: Integration Code
-
You can find the Integration code in the Integration Code tab in
the module. Just copy-paste that code snippet wherever you want to
access the user attributes.
-
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
aspnetsupport@xecurify.com
Step 7: Add the following link into your application for Single Sign-On
(SSO)
-
Use the following URL as a 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 8: 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 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
and 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 provide
DotNetNuke Single Sign-On SAML Connector.
Click here
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.
Additional Resources:
Setup Guide
Video Guide
