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

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

Steps to configure DNN Single Sign-On (SSO) using WHMCS 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 WHMCS as Identity Provider from the list. You can also search for your Identity Provider using the search box.

2. Configure WHMCS as OAuth Provider

• To configure OAuth Provider application, go to your WHMCS domain and log into your WHMCS Administrator account.
• You will be presented with following screen. Go to Setup OpenID Connect on the navigation bar on top.

• Click on Generate New Client API Credentials button.

• You will be redirected to the app details page. Fill in the required details and enter Authorized Redirect URIs from miniOrange ASP.NET OAuth Client and click on Generate Credentials.

• You will be brought to App details page. Here, you can find Client ID and Client Secret which you will require in Step 3 to configure miniOrange ASP.NET OAuth Client.



WHMCS Endpoints and Scope:




Client ID :	Click Here
Client Secret :	Click Here
Scope:	openid profile email
Authorize Endpoint:	https://{yourWHMCSdomain}/oauth/authorize.php
Access Token Endpoint:	https://{yourWHMCSdomain}/oauth/token.php
Get User Info Endpoint:	https://{yourWHMCSdomain}/oauth/userinfo.php

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

Additional Resources

• DNN OAuth Single Sign-On (SSO)
• DNN SAML Single Sign-On (SSO)
• ASP.NET OAuth Single Sign-On (SSO)
• nopCommerce OAuth Single Sign-On (SSO)
• nopCommerce SAML Single Sign-On (SSO)