SAML Single Sign-On (SSO) For ASP.NET Web Applications Using Okta As IDP

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.

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 Okta Single Sign-On (SSO) Login into ASP.NET

1. Add Okta in ASP.NET SAML Module

  • Go to Plugin settings section and Choose Okta from the list.
  • Okta SAML SSO , 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.
  •  ( Microsoft Azure AD) SAML SSO find metadata

2. Configure Okta as Identity Provider

miniorange img Configure Okta as IdP

  • Log in to Okta Developer Console.
  • In Okta Developer site, navigate to Applications tab and select Applications.
  • Configure Okta as IDP -SAML Single Sign-On(SSO) for WordPress - Okta SSO Login - add_application
  • Click on the Create App Integration button to create new app.
  • Configure Okta as IDP -SAML Single Sign-On(SSO) for WordPress - Okta SSO Login - SAML 2.0 Configure
  • Click on the SAML 2.0.
  • Configure Okta as IDP -SAML Single Sign-On(SSO) for WordPress - Okta SSO Login - SAML 2.0 Configure
  • In General Settings tab, enter App Name and click on Next button.
  • Configure Okta as IDP -SAML Single Sign-On(SSO) for WordPress - Okta SSO Login - SAML 2.0 Configure
  • In SAML Settings, enter the following:
  • Configure Okta as IDP -SAML Single Sign-On(SSO) for WordPress - Okta SSO 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 Group Attribute Statements (Optional) and click on Next button.
  • Configure Okta as IDP -SAML Single Sign-On(SSO) for WordPress - Okta SSO 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.
  • Configure Okta as IDP -SAML Single Sign-On(SSO) for WordPress - Okta SSO 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 ASP.NET SAML Module.
  • SAML Single Sign-On (SSO) using Okta as Identity Provider(IdP), Okta Login - Configure setup

3. Configure ASP.NET SAML Module as Service Provider

  • Go to the miniOrange ASP.NET SAML 2.0 SSO module and click on Upload IDP Metadata button.
  • Okta SAML SSO , go to module
  • In the Metadata URL option, Paste the Metadata URL which you have copied from your IDP and click on Fetch Metadata button.
  • Okta SAML SSO : metadata url
  • Click Save to save your IDP details.
  • Okta SAML SSO  : save button

4. User Attribute Mapping

User Attribute Mapping is mandatory for enabling users to successfully login into ASP.NET application. We will be setting up user profile attributes for ASP.NET applications using below settings.

  • Click on the Test Configuration button to test whether the SAML Configuration you’ve done is correct. On successful test configuration, you will get the different user attributes returned by your identity Provider in a test configuration table.
  • asp.net saml sso Okta: test configuration settings
    asp.net saml sso Okta: test configuration settings
  • Once you see all the values in test configuration table, click on Configure Attribute Mapping button.
  • asp.net saml sso Okta : attribute mapping
  • You will be redirected to the Attribute Mapping section where you can see that the user attribute as an autofield.
  • Note: All the mapped attributes will be stored in the session so that you can access them in your application.
  • Click on Save Attribute Mapping button.
  • asp.net saml sso Okta : attribute mapping

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 Okta: integration code

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>

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