ASP.NET SAML Single Sign-On (SSO)

ASP.NET Single Sign-On (SSO) module offers an easy way to integrate Single Sign-On (SSO) to your ASP.NET, SSO into ASP.NET MVC, SSO into ASP.NET Core, SSO into VB.NET, ASP Classic, Desktop and SAAS applications. The lightweight Single Sign-On (SSO) library helps you provide SSO access to cloud, intranet or on-premise websites using a single credentials entry.

Use cases supported with our SSO module

1. Windows Authentication:

ASP.NET SAML SSO Module has support for Integrated Windows Authentication(IWA). Integrated Windows Authentication is the preferred approach to authentication whenever users are part of the same Windows domain as the server. Users are authenticated against an existing identity store such as Active Directory which gives seamless login experience.

2. Single Sign-On (SSO) into Multiple applications:

ASP.NET SAML SSO Module also supports for login (asp.net sso) into multiple asp.net application with one IdP and one set of credentials using SAML protocol. Once the user will be logged into one of the applications, he/she will be logged into to asp.net application automatically that is no need to enter login credentials for other applications again.

3. Single Sign-On (SSO) into single custom ASP.NET / ASP.NET MVC / ASP.NET Core / VB.NET application:

ASP.NET SAML SSO module helps you to add functionality for Single Sign-On (SSO) to your ASP.NET, ASP.NET MVC, ASP.NET Core, VB.NET applications. Implementation of Single Sign On (SSO) in ASP.NET, ASP.NET MVC, ASP.NET Core, VB.NET applications will help you to protect your web application by providing authentication using your existing identity provider.

Benefits

Single Sign On

Easy and seamless access to all resources. ASP.NET Single Sign-On (SSO) via any existing SAML 2.0 Identity Provider

Protect Your Complete Site

You can restrict your site to only logged in users by redirecting the users to your IdP if logged in session is not found

Single Logout

Allows a user to logout from all server sessions established via SAML SSO by initiating the logout process once.

Attribute Mapping

Offers you to map the attributes from your IdP to your ASP.NET application

Role Mapping

Map your Identity Provider roles to your ASP.NET application and restrict resources to specific roles

Multiple IDP's Supported

Support SSO with multiple SAML Identity Providers

Custom Certificate

Add your own custom X.509 Certificate for sending signed Request and verification of signed Response.

Auto-sync IdP Configuration from metadata

Keep your IDP SAML Configuration and Certificates updated and in sync

Federation Support

Allows users to Single Sign On into the site via their institution that is affiliated with InCommon Federation

Azure AD

Azure B2C

Okta

ADFS

Office 365

Google Apps

You can enable Single Sign-On (SSO Login) into ASP.NET using our ASP.NET SAML SSO module through any SAML-compliant identity provider. We have integrated with popular identity providers like Azure AD, ADFS, Okta, WordPress, Office 365, Google Apps along with several other identity providers.

Our SSO Integrations

Can't find your IDP ? Contact us on aspnetsupport@xecurify.com. We'll help you set up ASP.NET SAML Single Sign-On (SSO) in no time.

WordPress

Auth0

One Login

Keycloak

miniOrange

Shibboleth

Plans For Everyone

License is linked to the domain of the ASP.NET instances or applications, so if you have dev-staging-prod type of environment then you will require 3 licenses of the plugin (with discounts applicable on pre-production environments). Contact us at aspnetsupport@xecurify.com for bulk discounts.
If you do not have an account with us already, please register here to proceed with the license purchase.

TRIAL

^$ 0
DOWNLOAD NOW
See the Free Plugin features list below
Unlimited Authentications
Basic Attribute Mapping (Username)
Custom Redirect URL after Login
Login link
Step by Step guide to setup IDP
-
-
-
-
-
-
-
-
-
-
-
-
-
Support 24x7
Contact Us

PREMIUM

^$ 449
BUY NOW
See the Premium Plugin features list below
Unlimited Authentications
Basic Attribute Mapping (Username)
Custom Redirect URL after Login
Login link
Step by Step guide to setup IDP
Protect Complete Site
Advanced Attribute Mapping(Email, FirstName, LastName)
SAML Single Logout
Custom Attribute Mapping
Customize SP Configuration
Use different Binding types [Http-Redirect Binding, Http-POST Binding]
Custom Redirect URL after Login/Logout
-
-
-
-
-
-
Support 24x7
Contact Us

ENTERPRISE

^$ 649^*
BUY NOW
See the Enterprise Plugin features list below
Unlimited Authentications
Basic Attribute Mapping (Username)
Custom Redirect URL after Login
Login link
Step by Step guide to setup IDP
Protect Complete Site
Advanced Attribute Mapping(Email, FirstName, LastName)
SAML Single Logout
Custom Attribute Mapping
Customize SP Configuration
Use different Binding types [Http-Redirect Binding, Http-POST Binding, Artifact Binding, SOAP Binding]
Custom Redirect URL after Login/Logout
**Multiple IDPs support
Header Based Authentication
Cookie based Authentication
Encrypted Assertion
Custom Certificates
Customized Login & Logout URL
Support 24x7
Contact Us

* Multiple IdP Support -

There is an additional cost for the number of Identity Providers you have.

Need Help? We do offer technical support!

* We provide deep discounts on bulk license purchases and pre-production environment licenses. As the no. of licenses increases, the discount percentage also increases.

Payment Methods

All of the payment methods listed below are supported by us. Payments can also be made through resellers. If you have a preferred reseller, we're happy to work with them.

Credit cards (American Express, Discover, MasterCard, and Visa) - If the payment is made through Credit Card/International Debit Card, the license will be created automatically once the payment is completed.

Please contact us here or drop an email at aspnetsupport@xecurify.com for more information

Please contact us here or drop an email at aspnetsupport@xecurify.com so that we can provide you the bank details.

Frequently Asked Questions

Does miniOrange offer technical support?

Yes, we provide 24*7 support for all and any issues you might face while using the plugin, which includes technical support from our developers. You can get prioritized support based on the Support Plan you have opted. You can check out the different Support Plans from here.

Does miniOrange store any user data?

miniOrange does not store or transfer any data which is coming from the Identity Provider to ASP.NET. All the data remains within your premises / server.

How will pricing work in a load balancer environment?

One (1) license will be sufficient for one application hosted on multiple servers behind a load balancer in load balancing environments. E.g. You’ve one (1) application running in a production environment, and the application is load balanced with two (2) servers behind load balancer. Here, only one license of the solution will be sufficient for you. Separate licenses are required to use the solution in other environments of the same application.

Does miniorange provide developer license for paid plugin?

We do not provide the developer license for our paid plugins and the source code is protected. It is strictly prohibited to make any changes in the code without having written permission from miniOrange. There are hooks provided in the plugin which can be used by the developers to extend the plugin's functionality

What is the licensing model?

Licensing for miniOrange plugins/modules/connectors is application instance-based and linked to the Fully Qualified Domain Name (FQDN) / unique URLs of the application(s). ‘Application implies an instance of software that is hosted and run on a server.

E.g. If you have separate apps for different purposes, both of these applications can be accessed with any one type of FQDN shown below:
1. domain1.com and domain2.com OR
2. app1.domain.com and app2.domain.com OR
3. domain.com/app1 and domain.com/app2 OR
4. test.domain.com/app1 and test.domain.com/app2

You’ll be required to have two separate licenses for each application. With pre-production environments (staging, user acceptance testing, and testing), you'll need separate licenses for each.

Steps to Configure the ASP.NET SAML 2.0 Module

Note: We recommend to install this library in your ASP.NET web application from NuGet store 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

Install from NuGet store
Manual Installation

NuGet Package
.NET CLI

PM> Install-Package miniOrange.SAML.SSO -Version 5.9.9

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.

ASP.NET SAML SSO - Copy SP Metadata manually

Step 3: Configure ASP.NET as Service Provider (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 Single Sign-On.

3.1: Share SAML Metadata with identity provider

Click on Add New IDP to configure ASP.NET 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.

ASP.NET SAML SSO - Select identity provider

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 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.

ASP.NET SAML SSO - 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.

ASP.NET SAML SSO - SAML dll Test configuration

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.

ASP.NET SAML SSO - Prefix SSO Attributes

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.

ASP.NET SAML SSO - ASP.NET Integration Codes Based on language

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 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 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. 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:

Need Help?

Not able to find your identity provider? Mail us on aspnetsupport@xecurify.comand 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.