DNN OAuth Single Sign-On (SSO) with Facebook as OAuth Provider

DNN OAuth Single Sign-On (SSO) authentication provider gives the ability to enable OAuth Single Sign-On for your DotNetNuke site. Using Single Sign-On you can use only one password to access your DotNetNuke site and services. Our authentication provider is compatible with all the OAuth compliant identity providers. Here we will go through a step-by-step guide to configure Single Sign-On (SSO) between DNN and Facebook considering Facebook as OAuth Provider. To know more about the other features we provide for DNN OAuth Single Sign-On (SSO), click here.

Pre-requisites: Download and Installation

• Download the DNN Oauth Single Sign On authentication provider with above link.
• Upload the installation package dnn-oauth-single-sign-on_xxx_Install by going in Settings > Extension > Install Extension.
• Now under the Installed extensions tab select Authentication Systems. Here you can see the miniOrange DNN OAuth Authentication Provider.

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

• Now go to the site settings tab. Here you can see the DNN OAuth Authentication Provider Dashboard.

• You have finished with the installation of the Authentication Provider on your DNN site.

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

1. Configure Authentication Provider for Setting up OAuth Single Sign-On (SSO)

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


Select your Identity Provider

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

2. Configure Facebook as OAuth Provider

• First of all, Login/ Signup in Facebook developer console at https://developers.facebook.com/

• Go to My apps.

• Click on Create app to create a new app.

• Select what your app is going to work for.

• Enter the required details and click on create app.

• Complete the security check and click on Submit button.

• Select Facebook Login by clicking on the set up button .

• Select Facebook Login -> Settings under Products option in the navigation bar.

• Enter the Callback/Redirect URL (from your DNN OAuth SSO module) in the Valid OAuth Redirect URIs field. Click on the Save button to save your configurations.
• Note: Your Callback/Redirect URI should be https and not http. It is mandatory while configuring Facebook as an OAuth Provider.

• Go to Settings -> Basic to view your App Id and App Secret as shown in the image below.

• Enter your Privacy Policy URL in the Privacy Policy URL field and choose a category from the dropdown in the Category field. Then, click on Save Changes button to save your configurations.
• Copy your App ID and your App Secret and save it in your DNN OAuth SSO module under the respective fields.

• Change you app status from In Development to Live by clicking on OFF as shown in the image below. Then, click on confirm to confirm your change of status.

You have successfully configured Facebook as OAuth Provider to Single Sign-On into your DNN application.

3. Configuring OAuth Provider

• Copy the Redirect/Callback URL and provide it to your OAuth provider.

4. Configuring OAuth Client

• Configure Client ID, Client Secret, update the endpoints if required and save the settings.

5. Test Configuration

• Now go to the Identity Provider Settings tab.
• Under the select actions click on the Test Configuration button to verify if you have configured the authentication provider correctly.

• On successful configuration, you will get Attribute Name and Attribute Values in the Test Configuration window.

6. Attribute Mapping

• For attribute mapping select the Edit Configuration from the select actions dropdown.
• Map email and username with Attribute Name you can see in Test Configuration window and save the settings.

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

• ASP.NET OAuth Single Sign-On (SSO)
• Two-Factor Authentication for ASP.NET
• Two-Factor Authentication for DNN
• DNN SAML Single Sign-On (SSO)
• DNN REST API Authentication
• nopCommerce OAuth Single Sign-On (SSO)
• Kentico SAML Single Sign-On (SSO)

×