SAML Single Sign-On (SSO) For ASP.NET Using Gluu Server As IDP

SAML Single Sign-On (SSO) For ASP.NET Using Gluu Server As IDP


ASP.NET SAML SP Single Sign-On (SSO) module gives the ability to enable SAML Single Sign-On for your ASP.NET applications. Using Single Sign-On you need only one password to access your ASP.NET application and services. Our module is compatible with all SAML compliant Identity Providers. Here, we will go through a step-by-step guide to configure Single Sign-On (SSO) between ASP.NET and Gluu Server, considering Gluu Server as IdP.

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.
  • saml dll register
  • Register or log in with your account by clicking the Register button to configure the module.

Steps to configure Gluu Server Single Sign-On (SSO) Login into ASP.NET

1. Add Gluu Server in ASP.NET SAML Module

  • Go to Plugin settings section and choose Gluu Server from the list.
  • asp.net saml sso using  Gluu Server as an idp, search idp
  • You will see the Service Provider Settings option, where you will get the service provider metadata. You can have three options to provide the metadata to your IdP. Keep the metadata handy as it will be required later to configure step 2.
  • asp.net saml sso using  Gluu Server as an idp, find metadata

2. Configure Gluu Server as Identity Provider

  • Login to Gluu server Admin Console.
  • From the navigation panel, click on SAMLAdd Trust Relationships.
  • Configure Gluu Server as IDP - SAML Single Sign-On(SSO) for ASP.NET - Gluu Server SSO Login Gluu Server SSO
  • Configure the following in Trust Relationship Form:
    • Display Name: ASP.NET SAML App (Enter any name for identifying the application)
    • Description: Provide a suitable description for you application
    • Entity Type: Single SP
    • Metadata Location: File
    • Configure Gluu Server as IDP - SAML Single Sign-On(SSO) for ASP.NET - Gluu Server SSO Login Gluu Server SSO 1
  • From the Service Provider Metadata tab in the plugin, download the Metadata XML File.
  • Upload the Metadata file in SP Metadata File.
  • Now tick the Configure Relying Party checkbox and click on Configure Relying Party link.
  • Configure Gluu Server as IDP - SAML Single Sign-On(SSO) for ASP.NET - Gluu Server SSO Login Gluu Server SSO 1
  • You will be shown the Relying Party Configurations page.
  • From Available Profile Configurations, select SAML2SSO and click on Add to add SAML2SSO to Selected Profile Configurations.
  • In SAML 2 SSO Profile, configure the following:
  • signAssertions Never
    signRequests Conditional
    encryptAssertions Conditional
    defaultAuthenticationMethods None
    Support Unspecified NameId Format Tick the checkbox
  • From Available NamedId Formats, select urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress and
    urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified and add it to the Selected NamedId Formats.
  • Click on Save button.
  • Configure Gluu Server as IDP - SAML Single Sign-On(SSO) for ASP.NET - Gluu Server SSO Login Gluu Server SSO 2
  • From the Release Additional Attributes section on the right, add the attributes you want to send to the Service Provider.
  • Click on Update button.
  • Configure Gluu Server as IDP - SAML Single Sign-On(SSO) for ASP.NET - Gluu Server SSO Login Gluu Server SSO 3
  • Gluu's SAML IDP metadata can be found at https://HOSTNAME/idp/shibboleth. This will be required to configure the plugin in Service Provider.

3. Configure ASP.NET SAML Module as Service 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

4. 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 Continue SSO Integration to continue further with the SSO Integration.
  • asp.net saml sso using Gluu Server as an idp, configure attribute mapping
  • If you are experiencing any error on the module end you’ll see the window shown below.
  • ASP.NET SAML SSO - Enable debug logs
  • To troubleshoot the error you can follow the steps below:
    • Under Troubleshoot 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 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.

5. Integration Code

  • You can also 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.
  • asp.net saml sso using Gluu Server as an idp, integration code

Note: If you need any assistance with adding the integration code in your application please reach out to us at aspnetsupport@xecurify.com.

6. Login Settings

  • Use the following URL as a link in your application from where you want to perform SSO:
  • https://<your-application-base-url>/?ssoaction=login
  • For example you can use it as:
  • <a href="https://<your-application-base-url>/?ssoaction=login">Login</a>

7. Logout Settings

  • Use the following URL as a link in your application from where you want to perform SLO:
  • https://<your-application-base-url>/?ssoaction=logout
  • For example you can use it as:
  • <a href="https://<your-application-base-url>/?ssoaction=logout">Logout</a>

You can configure the DotNetNuke 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.


If you are looking to Single Sign-On into your sites with any SAML compliant Identity Provider then we have a separate solution for that. We do provide SSO solutions for the following:

Application LINK
SAML SSO into DotNetNuke (DNN) site Click here
SAML SSO into Nopcommerce site Click here
SAML SSO into Umbraco site Click here
SAML SSO into SiteFinity site Click here

Additional Resources

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