DNN SAML Single Sign-On (SSO) Using PingFederate 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 PingFederate considering PingFederate 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.

1. Add module on DNN page

  • Open any of the page on your DNN site (Edit mode) and Click on Add Module.
  • DNN Ping Federate SAML SSO - add module
  • Search for DNNSAMLSSO and click on the DNNSAMLSSO. Drag and drop the module on the page where you want.

  • DNN Ping Federate SAML SSO - search module
  • You have finished with the Installation of the module on your DNN site.

2. Configure PingFederate as Identity Provider

Follow the steps below to configure PingFederate as IdP

miniorange img Configure PingFederate as IdP

  • In the miniOrange DNN SAML SSO Module, navigate to Service Provider Settings section. Here, you can find the SP metadata such as SP Entity ID and ACS (AssertionConsumerService) URL which are required to configure the Identity Provider.
  • DNN Ping Federate SAML SSO - upload metadata
  • Login to your Ping Federate User Admin dashboard.
  • Click on the Identity Provider in the left navigation menu.
  • Under SP CONNECTION, click on Create New button.
  • Select the Browser SSO Profiles connection template on the Connection Type tab and click Next.
  • DNN Ping Federate SAML SSO - Browser SSO Profiles
  • Select Browser SSO on the Connection Options tab and click Next.
  • DNN Ping Federate SAML SSO - Connection Options
  • Select File as the method for importing metadata and click Choose file to choose the miniOrange SSO plugin’s metadata on the Import Metadata tab. Click Next.
  • DNN Ping Federate SAML SSO - Import Metadata
  • Review the information on the Metadata Summary tab and click Next.
  • In the General Info tab ensure that the Service Provider’s Entity ID, Connection Name, and Base URL fields pre-populate based on the metadata. Click Next.
  • Navigate to the Browser SSO tab and click on the Configure Browser SSO. You will be redirected to Browser SSO Setup wizard.
    1. 1. Select the IdP-Initiated SSO and SP-Initiated SSO options on the SAML Profiles tab and clickNext.
    2. DNN Ping Federate SAML SSO - SAML Profiles
    3. 2. Enter your desired assertion validity time from on the Assertion Lifetime tab and click Next. By default, it is configured5minutes for both.
    4. 3. Navigate to the Assertion Creation and click on the Configure Assertion Creation. You will be redirected to the assertion creation setup wizard.
      • I. In the Identity Mapping tab select STANDARD and click Next.
      • II. Select a Subject Name Format for the SAML_SUBJECT on the Attribute Contract tab and click Next.
      • III. Click Map New Adapter Instance on the Authentication Source Mapping.
      • DNN Ping Federate SAML SSO - Authentication Source Mapping
      • IV. Select an Adapter Instance and click Next. The adapter must include the user’s email address.
      • DNN Ping Federate SAML SSO - Adapter Instance
      • V. Select the Use only the adapter contract values in the SAML assertion option on the     Mapping Method tab and click Next.
      • VI. Select your adapter instance as the Source and the email as the Value on the Attribute Contract Fulfilment tab and click Next.
      • DNN Ping Federate SAML SSO - Mapping Method
      • VII. (Optional) Select any authorization conditions you would like on the Issuance Criteria tab and click Next.
      • VIII. Click Done on the Summary.
      • IX. Click Next on the Authentication Source Mapping tab.
      • X. Click Done on the Summary tab.
      • XI. Click Next on the Assertion Creation
    5. Navigate to the Protocol Settings tab of the Browser SSO wizard and click on the Configure Protocol settings.

      • 1. Select POST for Binding and specify the single sign-on endpoint URL in the Endpoint URL field on the Assertion Consumer Service URL Click Next.
      • DNN Ping Federate SAML SSO - Browser SSO wizard
      • 2. Select POST on the Allowable SAML Bindings tab and click Next.
      • 3. Select your desired signature policies for assertions on the Signature Policy tab and click Next.

      • DNN Ping Federate SAML SSO - Allowable SAML Bindings
      • 4. Select your desired encryption policy for assertions on the Encryption Policy tab and click Next.
      • 5. Click Done on the Protocol Settings Summary tab.
      • 6. Click Done on the Browser SSO Summary.
  • Navigate to the Credentials and click on the Configure Credentials. You will be redirected to the Credentials setup wizard.
    • 1. Select the Signing Certificate to use with the Single Sign-On service and select Include the certificate in the signature element in the Digital Signature Settings tab. Click Done.
    • DNN Ping Federate SAML SSO - Signing Certificate
    • 2. Click Done on the Summary.
    • 3. Click Next on the Credentials.
  • Select Active for the Connection Status on the Activation & Summary tab and click Save.
  • Now, navigate to the Ping Federate User Admin dashboardè Identity Provide.
  • Click Manage All under SP Connections.
  • Click Export Metadata for the desired service provider connection.
  • Click Export on the Export & Summary tab and click Done.

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.

  • DNN Ping Federate SAML SSO - idp settings

4. Test Configuration

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

  • DNN Ping Federate SAML SSO - test configuration settings

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

  • DNN Ping Federate SAML SSO - add login button
  • Add Button name and Description for item and click on Save.

  • DNN Ping Federate SAML SSO - 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.

    • DNN Ping Federate SAML SSO - module settings
      dotnetnuke DNN Ping Federate SAML SSO - 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.

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.

  • DNN Ping Federate SAML SSO - 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.
  • DNN Ping Federate SAML SSO - 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.

Additional Resources

Need Help?

Not able to find your identity provider? Mail us on dnnsupport@xecurify.com and we'll help you set up SSO with your IDP and for quick guidance (via email/meeting) on your requirement and our team will help you to select the best suitable solution/plan as per your requirement.

Hello there!

Need Help? We are right here!

Contact miniOrange Support

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