nopCommerce OAuth Single Sign-On (SSO) with Google 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 Google considering Google 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 Google as Identity Provider

1. Configure Google as IDP

• Go to https://console.developers.google.com/ and sign up/login.
• Click on Select Project to create a new Google Apps Project,you will see a popup with the list of all your projects.

• You can click on the New project button to create new project.

• Enter your Project name under the Project Name field and click on Create.

• Go to Navigation MenuAPIsServicesCredentials.

• Click on Create Credentials button and then select OAuth Client ID from the options provided.

• In case you are facing some warning saying that in order to create an OAuth Client ID, you must set a product name on consent screen (as shown in below image). Click on the Configure consent screen button.

• Choose how you want to configure and register your app and click on create button.

• Enter the required details such as App Name, User Support Email. and click on Save and Continue button.

• Now for configuring scopes, click on Add or Remove the Scopes button.

• Now, Select the Scopes to allow your project to access specific types of private user data from their Google Account and click on Update button.

• Go to the Credentials tab and click on Create Credentials button. Select Web Application from dropdown list to create new application.

• Enter the name you want for your Client ID under the name field and enter the Redirect/Callback URI from miniOrange nopCommerce OAuth module under the Authorized redirect URIs field and click on Create button.

• You will see a popup with the Client ID and Client Secret Copy your Client ID and Client Secret and save it on your miniOrange nopCommerce OAuth plugin configuration.

You have successfully configured Google 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 Google 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 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)