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

DNN SAML Single Sign-On (SSO) module 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 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 DotNetNuke and Okta considering Okta as IdP.

Pre-requisites: Download and Installation

• Download the package for DNN SAML Single Sign-On (SSO) module.
• 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 module on DNN page

• Open any of the page on your DNN site (Edit mode) and Click on Add Module.

• Search for DNNSAMLSSO and click on the DNNSAMLSSO. Drag and drop the module on the page where you want.

• You have finished with the Installation of the module 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 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 Update to Save your IDP details.

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.

5. Adding Login/SSO Widget on DNN Page

• For Adding Button on the DNN page on beside the module settings click on the Add Item (Pencil Icon).

• Add Button name and Description for item and click on Save.

• You can see login button on the page after saving item. (If you are already logged in your site, you will see a "Logout" link).
• Note: If you want to Enable this button on every page of the DNN site follow below steps:
• Go to the Settings >> Module Settings >> Advanced Settings and Enable option for Display Module On All Page.

• Warning: You will lose all your configuration for the module after enabling this option. You can re-configure the module or it is better to enable this option before configuring the module.

6. Attribute Mapping

• Attributes are user details that are stored in your Identity Provider.
• Attribute Mapping helps you to get user attributes from your IdP and map them to DotNetNuke user attributes like firstname, lastname etc.
• While auto registering the users in your DotNetNuke site these attributes will automatically get mapped to your DotNetNuke user details.
• Go to DNNSAMLSSO Settings >> Advanced settings >> Attribute Mapping.

7. Role mapping (It is Optional to fill this)

• DotNetNuke uses a concept of Roles, designed to give the site owner the ability to control what users can and cannot do within the site.
• DotNetNuke has five pre-defined roles: Administrators, Subscribers, Registered Users, Translator (en-US) and Unverified Users.
• Role mapping helps you to assign specific roles to users of a certain group in your IdP.
• While auto registering, the users are assigned roles based on the group they are mapped to.

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.

8. 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)