nopCommerce OAuth Single Sign-On with Azure AD as OAuth Provider

nopCommerce OAuth Single Sign-On (SSO) module gives the ability to enable OAuth Single Sign-On for your nopCommerce store or site. Using Single Sign-On you can use only one password to access your nopCommerce store or site and services. Our module 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 nopCommerce and Microsoft Entra ID (formerly Azure AD) considering Azure AD as OAuth Provider.

Pre-requisites: Download and Installation

• Download the nopCommerce OAuth Single Sign-On (SSO) module.
• To install the plugin, login as admin into your nopCommerce site or store. In the admin dashboard, navigate to Configuration Tab >> Local plugins.
• On the top right corner of the page select the Upload plugin or theme button to upload the downloaded plugin zip. Follow the instructions further to install the plugin.

Steps to configure nopCommerce OAuth Single Sign-On (SSO) using Azure AD as Identity Provider

1. Configure Azure AD as IDP

• Sign in to Azure portal.
• Select Azure Active Directory.

• In the left-hand navigation pane, click the App registrations service, and click New registration.

• When the create page appears, enter your application's registration information.(Refer to the below table)

Name :	Name of your application.
Application type :	Select "Web app / API" for client applications and resource/API applications that are installed on a secure server. This setting is used for OAuth confidential web clients and public user-agent-based clients. The same application can also expose both a client and resource/API.
Redirect URI:	For "Web app / API" applications, provide the base URL of your app. eg, https://<domain-name> might be the URL for a web app running on your local machine. Users would use this URL to sign in to a web client application.

• When finished, click Register.

• Microsoft Entra ID (formerly Azure AD) assigns a unique Application ID to your application. The Application ID is your Client ID and the Directory ID is your Tenant ID, keep these values handy as you will need them to configure the miniOrange OAuth Client plugin.

• Go to Certificates and Secrets from the left navigaton panel and click on New Client Secret. Enter description and expiration time and click on ADD option.

• Copy the secret key "value" and keep the value handy it will be required later to configure Client Secret under the miniOrange nopCommerce OAuth Plugin.

You have successfully configured Microsoft Entra ID (formerly Azure AD) as OAuth Server (identity provider) for achieving SSO login into your nopCommerce application.

2. Configure nopCommerce as SP

• Under the Configure OAuth/OIDC tab, select Azure AD from the list of identity providers shown below

• When you are done configuring your identity provider, you will get client ID, client secret and all required authentication endpoints.
• Copy the Redirect/Callback URL from the plugin and provide it to your identity provider to configure it on their side.
• Fill the rest acquired details into the corresponding fields shown below:
• Click on Save.
• Note: Please make sure the Enable SSO checkbox is ticked.

3. Testing OAuth SSO

• Click here if you haven't already configured MFA on Azure AD. You can also disable MFA for Microsoft Entra ID (formerly Azure AD) by clicking here.
• Click on Test Configuration to verify if you have configured the plugin correctly.
• On successful configuration, you will get attributes name and attribute values in the test configuration window.

4. Attribute Mapping

• Under Attribute/Role Mapping tab, map the attribute names provided by your identity provider with your nopcommerce store attributes.
• Click on Save button.

5. Adding SSO link for your nopCommerce store

• Under the Redirection & SSO Link tab, use the URL labelled as Your Store SSO Link in your store to initiate the SSO.

You can even configure the Umbraco 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

• nopCommerce OAuth Single Sign-On (SSO)
• Web3 Login & NFT Gating for nopCommerce Applications
• ASP.NET SAML Single Sign-On (SSO)
• ASP.NET OAuth Single Sign-On (SSO)
• DNN OAuth Single Sign-On (SSO)
• DNN REST API Authentication
• Kentico SAML Single Sign-On (SSO)