Search Results :

×

ASP.NET SAML Single Sign-On Setup Guides

Which Setup Guide Should You Follow for Your Application?

If your application is built on the .NET Framework, please follow the detailed guide provided below. However, if your application is based on .NET Core, .NET 5, or later versions, we have a separate set of guides tailored specifically for these platforms. You can find out more about our Setup Guides by clicking on .NET Setup Guides button.



Choose your SAML identity provider to configure Single Sign-On (SSO)

Not able to find your IdP? Contact us at aspnetsupport@xecurify.com and we will help you setup ASP.NET SSO with your IdP in no time.

Couldn't find your IdP?

Reach out to us at aspnetsupport@xecurify.com and we will help you setup ASP.NET SSO with your identity provider (IdP) in no time.

ASP.NET SAML SSO - Office365 as IDP logo

Office365

ASP.NET SAML SSO - Google Apps as IDP logo

Google Apps

ASP.NET SAML SSO - Salesforce as IDP logo

Salesforce

ASP.NET SAML SSO - ClassLink as IDP logo

ClassLink

ASP.NET SAML SSO - Shibboleth-1 as IDP logo

Shibboleth-1

ASP.NET SAML SSO - Gluu Server as IDP logo

Gluu Server

ASP.NET SAML SSO - Absorb LMS as IDP logo

Absorb LMS

ASP.NET SAML SSO - Centrify as IDP logo

Centrify

ASP.NET SAML SSO - Salesforce Community as IDP logo

Salesforce Community

ASP.NET SAML SSO - Degreed as IDP logo

Degreed

ASP.NET SAML SSO - FusionAuth as IDP logo

FusionAuth

ASP.NET SAML SSO - CyberArk as IDP logo

CyberArk

ASP.NET SAML SSO - VMWare as IDP logo

VMWare

ASP.NET SAML SSO - miniOrange as IDP logo

miniOrange

ASP.NET SAML SSO - JumpCloud as IDP logo

JumpCloud

ASP.NET SAML SSO - WordPress as IDP logo

WordPress

ASP.NET SAML SSO - Shopify as IDP logo

Shopify

ASP.NET SAML SSO - Login.gov as IDP logo

Login.gov

ASP.NET SAML SSO - Magento as IDP logo

Magento

ASP.NET SAML SSO - Fonteva as IDP logo

Fonteva

ASP.NET SAML SSO - Shibboleth-2 as IDP logo

Shibboleth-2

Steps to Configure the ASP.NET SAML 2.0 Module

Step 1: Pre-requisites: Download and Installation


PM> NuGet\Install-Package miniOrange.SAML.SSO
  • 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.
  • ASP.NET SAML Single Sign-On (SSO) - saml dll register
  • 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.
  • ASP.NET SAML SSO - Copy SP Metadata
  • 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.
  • ASP.NET SAML SSO - Click on Add new IDP
  • 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.
  • ASP.NET SAML SSO - SP Settings Metadata

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:
  • ASP.NET SAML SSO - Upload Metadata
  • 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.
  • ASP.NET SAML SSO - SAML dll config

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.
  • ASP.NET SAML SSO - Enable debug logs
  • To troubleshoot the error you can follow the below steps:
    • Under Troubleshooting tab, enable the toggle to receive the plugin logs.
    • ASP.NET SAML SSO - Enable debug 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.
  • ASP.NET SAML SSO - ASP.NET Integration Codes Based on language
  • 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.

Hello there!

Need Help? We are right here!

support
Contact miniOrange Support
success

Thanks for your inquiry.

If you dont hear from us within 24 hours, please feel free to send a follow up email to info@xecurify.com