DNN SAML Single Sign-On (SSO) with Okta As IDP

DNN SAML Single Sign-On (SSO) authentication provider gives the ability to enable SAML Single Sign-On for your DotNetNuke applications. Using Single Sign-On you can use only one password to access your DotNetNuke application and services. Our authentication provider 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 DotNetNuke and Okta considering Okta as IdP.

Pre-requisites: Download and Installation

• Download the package for DNN SAML Single Sign-On (SSO) authentication provider.
• Upload the installation package dnn-saml-single-sign-on_xxx_Install by going in Settings > Extension > Install Extension.

Steps to configure DNN SAML Single Sign-On (SSO) using Okta as IDP

1. Add authentication provider on DNN page

• Now under the Installed extensions tab select Authentication Systems.Here you can see the miniOrange DNN SAML Authentication Plugin.

• Just Click on the pencil icon as mentioned in the image below to configure the DNN SAML Authentication Provider.

• You have finished with the Installation of the authentication provider on your DNN site.

2. Configure Okta as Identity Provider

Follow the steps below to configure Okta as IdP

 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.

• Log in to Okta Developer Console.
• In Okta Developer site, navigate to Applications tab and select Applications.

• Click on the Create App Integration button to create new app.

• Click on the SAML 2.0.

• In General Settings tab, enter App Name and click on Next button.

• In SAML Settings, enter the following:


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.


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

 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.

• After assigning the people/groups to your app, go to Sign On tab.
• Under SAML Signing Certificates, click on View SAML 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.

3. Configure DotNetNuke SAML Authentication Provider as Service Provider

• For configuring application in the authentication provider, click on the Add new IdP button in the Identity Provider Settings tab.


A] Select your Identity Provider

• Select Okta from the list.You can also search for your Identity Provider using the search box.


B] Configure your Identity Provider

• Under the Service Provider Settings tab, you can download SP metadata as a XML document or copy the metadata url.
• Alternatively, copy and paste the SP Entity ID and ACS Url from the SP metadata Table to your Okta configuration page.


C] Configure your Service Provider

• To upload IdP's metadata, you can use the Upload IdP metadata button under the Identity Provider Settings tab, if you have the IdP metadata URL or the IdP metadata .xml file.
• Alternatively, you can copy the IDP Entity ID and Single Sign-On Url values from the IdP and fill them up under the Identity Provider Settings tab.

4. Testing SAML SSO

• Click the Test Configuration button to verify if you have configured the plugin correctly.
• On successful configuration, you will get Attribute Name and Attribute Values in the Test Configuration window.

You can even configure the ASP.NET 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.

Additional Resources

• DNN SAML Single Sign-On (SSO)
• DNN OAuth Single Sign-On (SSO)
• ASP.NET SAML Single Sign-On (SSO)
• nopCommerce SAML Single Sign-On (SSO)
• Umbraco SAML Single Sign-On (SSO)