Search
START TYPING AND PRESS ENTER TO SEARCH

SAML Single Sign-On (SSO) For ASP.NET Web Applications Using Okta 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 can use only one password to access your ASP.NET application and services. Our module is compatible with all the SAML compliant Identity providers. Here we will go through a step-by-step guide to configure Single Sign-On (SSO) between ASP.NET and Okta considering Okta as IdP.

Download And Extract Package

  • Download miniOrange ASP.NET SAML 2.0 Module.
  • For Setting up the module, extract the asp-net-saml-sso-module-xxx.zip, you will find a DLL file miniorange-saml-sso.dll, a configuration file saml.config and a integration.md file which contain the steps for adding the module into your application.

Step 1: Add module in your application

  • Add miniorange-saml-sso.dll in the bin folder (where your other DLL files exist) for your application.
  • Register miniorangesamlsso module in your application according to the provided steps in the integration.md file.
  • Add the provided configuration file saml.config in the root directory for your application.
  • After integration open browser and browse the module dashboard with URL below:
      • https://<your-application-base-url>?ssoaction=config
  • If it pops up the registration page or login page, you have successfully added the miniOrange saml sso module for your application.

    • asp.net saml sso azure ad : login page
  • Register or Login for configuring the module.

Step 2: Configure Okta as Identity Provider

Follow the steps below to configure Okta as IdP

miniorange img Configure Okta as IdP

  • In the miniOrange SAML SP SSO plugin, navigate to Service Provider Metadata tab. Here, you can find the SP metadata such as SP Entity ID and ACS (AssertionConsumerService) URL which are required to configure the Identity Provider.
    • WordPress SAML Single Sign-On (SSO) upload metadata
  • Log into Okta Admin Console. Select "Classic UI" and then Application.
    • SAML Single Sign-On (SSO) using Okta as Identity Provider(IdP), Okta SSO Admin_Dashboard
  • Click on Add Applications.
    • SAML Single Sign-On (SSO) using Okta as Identity Provider(IdP), Okta Login - add_application
  • Click on Create New App.
  • Click on the SAML 2.0.
    • SAML Single Sign-On (SSO) using Okta as Identity Provider(IdP), Okta Login - SAML 2.0 Configure
  • In General Settings, enter App Name and click on Next.
  • In SAML Settings, enter the following:
    • SAML Single Sign-On (SSO) using Okta as Identity Provider(IdP), Okta Login - SAML_SETTINGS
    Single Sign On URL Enter ACS (AssertionConsumerService) URL from the Service Provider metadata tab of the module.
    Audience URI (SP Entity ID) Enter SP Entity ID / Issuer from the Service Provider Metadata tab of the module.
  • Configure Attribute Statements and Group Attribute Statement (Optional).
    • SAML Single Sign-On (SSO) using Okta as Identity Provider(IdP), Okta Login - Add_Attributes
  • If you have integrated your Active Directory in Okta and want to map the AD groups, please make sure that you have added the OUs used to import groups.You will also need to map the memberOf
    attribute under the integrated directory’s configuration.

miniorange im g Assigning Groups/People

  • After creating and configuring the app go to the Assignment Tab in Okta.
  • Here we select the peoples and groups you want to give access to log in through this app. Assign this to the people/group you would to give access to.
    • SAML Single Sign-On (SSO) using Okta as Identity Provider(IdP), Okta Login - Assign_groups
  • After assigning the people/groups to your app, go to Sign On tab.
  • Click on View Setup Instructions to get the SAML Login URL (Single Sign on URL), Single Logout URL, IDP Entity ID and X.509 Certificate. You will need this to configure the Service Provider.
    • SAML Single Sign-On (SSO) using Okta as Identity Provider(IdP), Okta Login - Configure setup

Step 3: Configure ASP.NET SAML Module as Service Provider

  • After configuring your Identity Provider, it will provide you with IDP Entity ID, IDP Single Sign On URL and x.509 Certificate. Configure these values under IDP Entity ID, Single Sign-On Url and SAML X509 Certificate fields respectively. (Refer to the Metadata provided by Identity Provider)
  • Click Save to Save your IDP details.

    • asp.net saml sso azure ad : idp settings

Step 4: Test Configuration

  • Click on the Test Configuration button to test the configuration.

    • asp.net saml sso azure ad : test configuration settings

Step 5: Attribute Mapping

  • After testing the configuration, Map your application attributes with the Identity Provider (IdP) 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 azure ad : attribute mapping

Step 6: 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 azure ad : integration code

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

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


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 SiteFinity site Click here
SAML SSO into Umbraco site Click here
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