SAML Single Sign-On (SSO) For DotNetNuke Sites Using Azure AD As IDP

DotNetNuke SAML SP 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 Azure AD considering Azure AD as IdP.

Download and Install the module in DotNetNuke

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

Step 1: Add module on DNN page

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

  • dotnetnuke dnn saml sso azure ad : add module
  • Search for DNNSAMLSSO and click on the DNNSAMLSSO. Drag and drop the module on the page where you want.

  • dotnetnuke dnn saml sso azure ad : search module
  • You have finished with the Installation of the module on your DNN site.

Step 2: Configure Azure AD as Identity Provider

  • Login into Azure AD Portal
  • Select Azure Active Directory -> App Registrations. Click on New Application Registration.

  • dotnetnuke dnn saml sso azure ad : new application
  • You will need SP Entity ID and ACS URL values while configuration. Refer to the below image:

  • dotnetnuke dnn saml sso azure ad : sp settings
  • After Clicking on New Registration, enter a Name for your application and choose the account type.
  • In the Redirect URI field, provide the ACS URL provided in the Service Provider Settings section of the module and click on the Register button.

  • dotnetnuke dnn saml sso azure ad : register app
  • After registering your application, go to Expose an API menu option and Click the Set button and replace the Application URI with the plugin's SP Entity ID provided in plugin’s Service Provider Settings.

  • dotnetnuke dnn saml sso azure ad : sp entity id
  • After setting the Application ID, go back to Azure Active Directory -> App Registrations window and click on Endpoints.
  • dotnetnuke dnn saml sso azure ad : endpoints
  • This will open up a window with multiple URLs listed there. Copy the Federation Metadata Document URL. This will be required while configuring the SAML module.

  • dotnetnuke dnn saml sso azure ad : metadata
  • Login into Azure AD Portal
  • Select Azure Active Directory -> Enterprise Applications. Click on New Application Application.

  • dotnetnuke dnn saml sso azure ad : enterprise app
    dotnetnuke dnn saml sso azure ad : new enterprise app
  • Click on the Non-gallery application section and enter the name for your app and click on Add button.

  • dotnetnuke dnn saml sso azure ad : non-gallery app
    dotnetnuke dnn saml sso azure ad : non-gallery app name
  • Click on Single sign-on from the application's left-hand navigation menu and select SAML.

  • dotnetnuke dnn saml sso azure ad : saml app
  • Edit BASIC SAML CONFIGURATION and enter the SP Entity ID for Identifier and the ACS URL for Reply URL from Service Provider Info tab of the plugin.

  • dotnetnuke dnn saml sso azure ad : edit basic saml configuration
  • Copy App Federation Metadata Url. This will be used while configuring the DotNetNuke SAML module.

  • dotnetnuke dnn saml sso azure ad : metadata url
  • Assign users and groups to your SAML application.
    • Click on Users and groups from the applications left-hand navigation menu.
    • After clicking on Add user, Select Users and groups in the Add Assignment screen. Search or invite an external user. Select the appropriate user and click on the Select button.
    • After selecting the appropriate user, click on the Assign button.
    • dotnetnuke dnn saml sso azure ad : add users

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

  • dotnetnuke dnn saml sso azure ad : idp settings

Step 4: Test Configuration

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

  • dotnetnuke dnn saml sso azure ad : test configuration settings

Step 5: Adding Login Widget on DNN Page

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

  • dotnetnuke dnn saml sso azure ad : add login button
  • Add Button name and Description for item and click on Save.

  • dotnetnuke dnn saml sso azure ad : save login button
  • 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.

    • dotnetnuke dnn saml sso azure ad : module settings
      dotnetnuke dnn saml sso azure ad : display module on multipages
    • 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.

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

  • dotnetnuke dnn saml sso azure ad : attribute mapping

Step 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.
  • dotnetnuke dnn saml sso azure ad : role mapping

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