nopCommerce SAML Single Sign-On (SSO) with Azure B2C as IDP

nopCommerce SAML Single Sign-On (SSO) plugin gives the ability to enable SAML Single Sign-On for your nopCommerce applications. Using Single Sign-On you can use only one password to access your nopCommerce application and services. Our plugin 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 nopCommerce and Azure B2C considering Azure B2C as IdP. To know more about the features we provide for nopCommerce SSO, click here.

Pre-requisites : Download And Installation

Download from nopCommerce Dashboard

• To download the plugin zip, login as admin into your nopCommerce store. In the admin dashboard, go to Configuration Tab > All Plugins and Themes or search for All Plugins and Themes in the Admin search bar.
• Search for the SAML Single Sign-On (SSO) - miniOrange plugin and click the Download button to get the zip.


From nopCommerce marketplace

• You can download the plugin zip file from nopCommerce store - nopCommerce SAML Single Sign-On (SSO)
• To install the plugin, login as admin into your nopCommerce website. In the admin dashboard, go 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 Single Sign-On (SSO) using Azure B2C as Identity Provider

1. Configure Azure B2C as IDP

• You need to send your SP metadata to identity provider, Azure B2C. For SP metadata, use the SP metadata URL or download the SP metadata as a .xml file and upload it at your IdP end. You can find both these options under the Service Provider Metadata tab.

• Alternatively, you can manually add the SP Entity ID and ACS URL from Service Provider metadata tab in the plugin to your IdP configurations.

 Register the Identity Experience Framework application

• Login into Azure B2C Portal.
• From the Azure AD B2C tenant, select App registrations, and then select New registration.

• For Name, enter IdentityExperienceFramework.
• Under Supported account types, select Accounts in this organizational directory only.

• Under Redirect URI, select Web, and then enter "https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com", where your-tenant-name is your Azure AD B2C tenant domain name.

NOTE:

In the following step if the 'Permissions' section is not visible then it might be the reason that you don't have an active AzureAD B2C subscription for that tenant. You can find the details regarding the AzureAD B2C subscription here and you can create a new tenant by following the steps here.



• Under Permissions, select the Grant admin consent to openid and offline_access permissions check box.
• Select Register.

• Record the Application (client) ID for use in a later step.

 Register the Identity Experience Framework application

• Under Manage, select Expose an API.
• Select Add a scope, then select Save and continue to accept the default application ID URI.

• Enter the following values to create a scope that allows custom policy execution in your Azure AD B2C tenant:
1. Scope name: user_impersonation
2. Admin consent display name: Access IdentityExperienceFramework
3. Admin consent description: Allow the application to access IdentityExperienceFramework on behalf of the signed-in user.
• Select Add scope

 Register the ProxyIdentityExperienceFramework application

• Select App registrations, and then select New registration.
• For Name, enter ProxyIdentityExperienceFramework.
• Under Supported account types, select Accounts in this organizational directory only.

• Under Redirect URI, use the drop-down to select Public client/native (mobile & desktop).
• For Redirect URI, enter myapp://auth.
• Under Permissions, select the Grant admin consent to openid and offline_access permissions check box.
• Select Register.

• Record the Application (client) ID for use in a later step.

 Next, specify that the application should be treated as a public client

• Under Manage, select Authentication.
• Under Advanced settings, enable Allow public client flows (select Yes).
• Select Save.

 Now, grant permissions to the API scope you exposed earlier in the IdentityExperienceFramework registration

• Under Manage, select API permissions.
• Under Configured permissions, select Add a permission.

• Select the My APIs tab, then select the IdentityExperienceFramework application.

• Under Permission, select the user_impersonation scope that you defined earlier.
• Select Add permissions. As directed, wait a few minutes before proceeding to the next step.

• Select Grant admin consent for (your tenant name).

• Select your currently signed-in administrator account, or sign in with an account in your Azure AD B2C tenant that's been assigned at least the Cloud application administrator role.
• Select Yes.
• Select Refresh, and then verify that "Granted for ..." appears under Status for the scopes - offline_access, openid and user_impersonation. It might take a few minutes for the permissions to propagate.

 Register the nopCommerce Application

• Select App registrations, and then select New registration.
• Enter a Name for the application such as: WP-app.
• Under Supported account types, select Accounts in any organizational directory or any identity provider. For authenticating users with Azure AD B2C.

• Under Redirect URI, select Web, and then enter the ACS URL from the Service Provider Metadata tab of the miniOrange nopCommerce SAML plugin.
• Select Register.

• Under Manage, click on Expose an API.
• Click on Set for the Application ID URI and then click on Save, accepting the default value.

• Once saved, copy the Application ID URI and navigate to the Service Provider Metadata tab of the plugin.
• Paste the copied value under the SP Entity ID / Issuer field provided in this tab.
• Click on Save.

 Generate SSO Policies

• From our Azure B2C portal, navigate to the Overview section of your B2C tenant and record your tenant name.
  NOTE: If your B2C domain is b2ctest.onmicrosoft.com, then your tenant name is b2ctest.

• Enter your Azure B2C tenant name below, along with the application ID for IdentityExperienceFramework and
  ProxyIdentityExperienceFramework apps as registered in the above steps.



Azure B2C tenant Name:
IdentityExperienceFramework app ID:
ProxyIdentityExperienceFramework app ID:
Select additional attributes	User Type Job Title Department Usage Location Street Address State or Province Country or Region City ZIP or Postal Code Office Phone Mobile Phone physicalDeliveryOfficeName Age Group Consent Provided for Minor Legal Age Group Classification createdDateTime netId



• Click on the Generate Azure B2C Policies button to download the SSO policies.
• Extract the downloaded zip file. It contains the policy files and certificate (.pfx), which you will require in the following steps.

 Setup and upload Certificates

• Sign in to the Azure portal and browse to your Azure AD B2C tenant.

• Under Policies, select Identity Experience Framework and then Policy keys.

• Select Add, and then select Options > Upload
• Enter the Name as SamlIdpCert. The prefix B2C_1A_ is automatically added to the name of your key.

• Using the upload file control, upload your certificate that was generated in the above steps along with the SSO policies (tenantname-cert.pfx).
• Enter the certificate's password as your tenant name and click on Create. For example, if your tenant name is xyzb2c.onmicrosoft.com, enter the password as xyzb2c
• You should be able to see a new policy key with the name B2C_1A_SamlIdpCert.

 Create the signing key

• On the overview page of your Azure AD B2C tenant, under Policies, select Identity Experience Framework.
• Select Policy Keys and then select Add.
• For Options, choose Generate.
• In Name, enter TokenSigningKeyContainer.
• For Key type, select RSA.
• For Key usage, select Signature.

• Select Create.

 Create the encryption key

• On the overview page of your Azure AD B2C tenant, under Policies, select Identity Experience Framework.
• Select Policy Keys and then select Add.
• For Options, choose Generate.
• In Name, enter TokenEncryptionKeyContainer.
• For Key type, select RSA.
• For Key usage, select Encryption.

• Select Create.

 Upload the policies

• Select the Identity Experience Framework menu item in your B2C tenant in the Azure portal.

• Select Upload custom policy.

• As per the following order, upload the policy files downloaded in the above steps:
• TrustFrameworkBase.xml
• TrustFrameworkExtensions.xml
• SignUpOrSignin.xml
• ProfileEdit.xml
• PasswordReset.xml
• SignUpOrSigninSAML.xml
• As you upload the files, Azure adds the prefix B2C_1A_ to each.

You have successfully configured Azure B2C as SAML IdP (Identity Provider) for achieving Azure B2C SSO login into your nopCommerce application.

2. Configure nopCommerce as SP

Note: After installation of the plugin, we need to setup the trust between your nopCommerce application and your Azure B2C account. SAML metadata is shared with Azure B2C so they can update their inbuilt configuration to support Single Sign-On.

2.1: Share SP SAML metadata with Azure B2C

• Click on Add New IDP to configure nopCommerce Single Sign-On (SSO) using Azure B2C as IDP.

• Under Service Provider Metadata tab, you can either copy-paste the metadata URL on your IDP side or download the SP metadata as an XML file. Additionally, you have the choice to manually copy and paste Base URL, SP Entity ID, and ACS URL.
• Share SAML metadata with Azure B2C.

2.2: Import Azure B2C SAML metadata

• Under Identity Provider Settings tab, select Azure B2C as your preferred identity provider.

• There are two methods for configuring nopCommerce as service provider:
• To upload IDP's metadata, you can either provide the metadata URL or upload XML file.

• Alternatively, under the Identity Provider Settings tab, you can manually fill in the mandatory fields like IDP Name, IDP Entity ID and Single Sign-On URL and hit Save.

3. Testing SAML SSO

• Before testing, please ensure the following:
• The nopCommerce (SP) SAML metadata has been exported to Azure B2C (IDP).
• Importing the Azure B2C (IDP) SAML metadata in nopCommerce (SP).
• Click here if you haven't already configured MFA on Azure B2C. You can also disable MFA for Azure B2C by clicking here.
• Hover on Select Action and click on the Test Configuration button to verify if you have configured the plugin correctly.

• Click the Test Configuration button to verify if you have configured the plugin correctly.
• On successful configuration, you will get Attribute Name and Attribute Values in Test Configuration window.

4. Attribute Mapping

• After successful test configuration, click on Edit Configuration and navigate to Attribute Mapping section.
• On the right side, you can see the IDP response table, map attribute names provided by your IDP with your store attributes, under Attribute/Role Mapping tab.
• Click on Save button.

5. Enabling SSO in your nopCommerce store

• Enable SSO for your nopCommerce store by dragging the slider as shown below.

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

Additional Resources

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