ASP.NET SAML Single Sign-On Setup Guides

Step 1: Download and extract the package

• 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 ASP.NET SAML Single Sign-On Plugin

Note: After installation of the plugin, we need to setup the trust between your ASP.NET application and your desired identity or partner provider.
SAML metadata is shared with partner providers so they can update their inbuilt configuration to support Single Sign-On.

Step 2.1: Share SP SAML metadata with partner provider

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

• Under Service Provider Settings 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 2.2: Import partner's SAML Metadata

• Select your preferred identity provider from the list shown below.

• There are two methods for configuring ASP.NET as service provider:

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 3: Testing SAML SSO

• 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 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 4: Integration Code

• You can find the Integration code in the Login Settings 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 5: 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 6: 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>