DNN SAML Single Sign-On (SSO) with ADFS as IDP

Overview

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 ADFS considering ADFS as IdP.

Configuration Steps

Step by Step guide for DNN SAML SSO using ADFS as Identity Provider.

1. Provide DNN SAML Metadata to ADFS Identity Provider

Steps to Configure ADFS IdP

• First, search for ADFS Management application on your ADFS server.

• In ADFS Management, select Relying Party Trust and click on Add Relying Party Trust.

• Select Claims aware from the Relying Party Trust Wizard and click on Start button.

Select Data Source

• In Select Data Source, select the data source for adding a relying party trust.

• Metadata URL
• Metadata XML file
• Manual Configuration

• Navigate to Service Provider Metadata section of the DNN plugin and copy the Metadata URL, which you will get from Step 2A.
• Select Import data about the relying party published online or on the local network option and add the metadata URL in Federation metadata address.
• Click on Next.

• Navigate to Service Provider Metadata section of the DNN plugin and click on the Download button to download the plugin metadata file, which you will get from Step 2A.
• Select Import data about the relying party from a file option and upload the downloaded metadata file.
• Click on Next.

• Navigate to Service Provider Metadata section of the DNN plugin to get the endpoints to configure Service Provider manually, which you will get from Step 2B.
• In Add Relying Party Trust Wizard select option Enter data about the relying party manually and click on Next.

Specify Display Name

• Enter Display Name and Click Next.

Configure Certificate (Premium feature)

• Download the certificate from Service Provider Metadata Tab, which you will get from Step 2A.
• Upload the certificate and click on Next.

Configure URL

• Select Enable support for the SAML 2.0 WebSSO protocol option and enter ACS URL from the plugin's Service Provider Metadata Tab, which you will get from Step 2B.
• Click on Next.

Configure Identifiers

• In the Relying party trust identifier, add the SP-EntityID / Issuer from the plugin's Service Provider Metadata tab, which you will get from Step 2B.

Choose Access Control Policy

• Select Permit everyone as an Access Control Policy and click on Next.

Ready to Add Trust

• In Ready to Add Trust click on Next and then Close.

Edit Claim Issuance Policy

• In the list of Relying Party Trust, select the application you created and click on Edit Claim Issuance Policy.

• In Issuance Transform Rule tab click on Add Rule button.

Choose Rule Type

• Select Send LDAP Attributes as Claims and click on Next.

Configure Claim Rule

• Add a Claim Rule Name and select the Attribute Store as required from the dropdown.
• Under Mapping of LDAP Attributes to outgoing claim types, Select LDAP Attribute as E-Mail-Addresses and Outgoing Claim Type as Name ID.

• Once you have configured the attributes, click on Finish.
• After configuring ADFS as IDP, you will need the Federation Metadata to configure your Service Provider.
• To get the ADFS Federation Metadata, you can use this URL
  https://< ADFS_Server_Name >/federationmetadata/2007-06/federationmetadata.xml
• You have successfully configured ADFS as SAML IdP (Identity Provider) for achieving ADFS Single Sign-On (SSO) Login

Windows SSO (Optional)

Follow the steps below to configure Windows SSO

• Steps to configure ADFS for Windows Authentication
  • Open elevated Command Prompt on the ADFS Server and execute the following command on it:
    setspn -a HTTP/##ADFS Server FQDN## ##Domain Service Account##
  • FQDN is Fully Qualified Domain Name (Example : adfs4.example.com)
  • Domain Service Account is the username of the account in AD.
  • Example : setspn -a HTTP/adfs.example.com username/domain.

• Open AD FS Management Console, click on Services and go to the Authentication Methods section. On the right, click on Edit Primary Authentication Methods. Check Windows Authentication in Intranet zone.

• Open Internet Explorer. Navigate to Security tab in Internet Options.
• Add the FQDN of AD FS to the list of sites in Local Intranet and restart the browser.
• Select Custom Level for the Security Zone. In the list of options, select Automatic Logon only in Intranet Zone.

• Open the powershell and execute following two commands to enable windows authentication in Chrome browser.

 Set-AdfsProperties -WIASupportedUserAgents ((Get-ADFSProperties | Select -ExpandProperty  WIASupportedUserAgents) + "Chrome")
 Get-AdfsProperties | Select -ExpandProperty WIASupportedUserAgents;


• You have successfully configured ADFS for Windows Authentication.

2. Configure ADFS Identity Provider Metadata in DNN SAML SSO

• Click on the Add new IDP button to configure a new Identity Provider.

• Under the Plugin Settings tab, select ADFS as your identity provider from the list shown.

• User gets logged in to the DNN site by entering the credentials of ADFS.

Related Articles

• DNN SAML SSO
• DNN SAML SSO Using miniOrange As IDP
• DNN SAML SSO with Okta As IDP