Setting up Azure AD  

Status
colour Blue title Step 1

To enable the Azure AD (OIDC) feature in Storefront, please proceed with the following guide:
Go to this link https://portal.azure.com/ and click on the "Azure Active Directory".

Click on "App registrations" option, from the Manage menu.

Then click on the "+ New registration" button to register an application.

On the following window, enter a name for your application under the Name text field. Example: "My Open Id Connect"

After you have chosen one of the three Supported account types, you can continue by clicking on the "Register" button.

From the next window, copy and store for later use, the following two IDs:

• "Application (client) ID"
• "Directory (tenant) ID"

Back to the Manage menu, click on the "Certificates & secrets" and create a " + New client secret". 
Copy and store, for later use, the "Key Value" that was created.

Image Modified

Setting up the BSS Mechanism  

Status
colour Blue title Step 2

Now on BSS, go to: BSS Setup > Administration > System Options > Storefront Login Settings (as explained on this Documentation). 
Click on the "Settings (OIDC)" button.

ID and Secret - Setup

On the following page, you are required to utilize the previously-stored IDs from "Step 1" and paste them to their corresponding fields. More specifically:

• Provide a name to the Instance Name text field.  

• Paste the following link, along with your stored [Directory (tenant) ID], i.e. "https://login.microsoftonline.com/[Directory (tenant) ID]/v2.0" to the Authority text field.
  

  Rw ui textbox macro
  type note
  The Issuer field was changed to the Authority field Please note that the Authority text field was formerly the Issuer text field. Consequently, if you fill in the Authority field with the [Directory (tenant) ID], you need to leave blank the Issuer field, because it is used only for backward compatibility reasons. However, the Issuer field can be populated only for Multi-Tenant configurations such as the ones that follow.

  
  

• Paste your stored [Application (client) ID] to the Client Id text field.
• Paste your stored [Key Value] to the Client Secret text field.
• Then click on the Save button.
  
  

Now that you have saved those settings you can copy and store, for later use, the following two URLs:

• The "Callback Url".
• The "Logout Url".
  
  

Attribute Mapping - Setup

Concerning the Attribute Mapping section of this page, it is introduced as an easy way to map the JSON response of the identity provider to a Property of the BSS Account/Contact/User.

Next to the first five attribute-mapping fields, there is a question mark icon, that upon hovering over it, it displays the default mapping values for your aid.

You don't need to fill in the Attribute Mapping text fields, since the attributes "ExternalId", "First Name", "Last Name", "Email", and "Phone" already have the default mapping (claims), which you can witness below.

However, if you wish to alter the default mapping, you can do so with either of the two JSON response objects namely IdToken, UserInfo that are utilized for the attribute mapping and the attribute matching. 
Please also note that many Attribute Mapping fields can be declared with a comma "," and the priority with which they are written applies (if no value is found in the first, the code checks the second).
Below you will find the two aforementioned JSON files that can be used as an example.

As it is evident from the JSON files, any extra parameter set at the OIDC provider, can be placed within the ExtraParameters.
For example, if you want to set the Company Name based on the value of the "cp1" field, then as mapping you must set "IdToken.ExtraParameters.extension_cp_gan". The same logic applies to any other extra parameters that are needed.

Attribute Matching - Setup

Concerning the Attribute Matching section of this page, it is one of the most important functionalities during the registration process, because after filling in the Account Code field, there will be a check via the identity provider's response on whether an account exists under the Azure Portal with that specific account code, or not. If a match is found between a BSS account and an identity provider's account, then there will be no need for registration on our systems. However, if no match is found, then the registration on our systems is required. 

Advanced Settings - Setup

Concerning the Advanced Settings section of this page, it is the most important option during the registration process, because this checkbox, if enabled, can allow the BSS registration process to be initiated in the event that a matching account(based on the "Account Code" entered in the previous section) has not been found during the check between the BSS and the identity provider. In its default disabled state, the checkbox will not allow the BSS registration process to be initiated, and the authentication will not proceed.

Image RemovedImage Added

Saving Configured Changes

After you have finished with this page's configuration, you must click on the "Save" button. 

Now that you have saved all those aforementioned settings of this page, you can copy and store, for later use, the following URL:

• The "Callback Url".

Setting up of Azure AD - Continued 

Status
colour Blue title Step 3

Now, by going back to the https://portal.azure.com/ you can perform the next seven easy actions:

• Click on "Azure Active Directory"
• Click on "App registrations" option, from the Manage menu.
• Find the application with name "My Open Id Connect" or any other name that you have assigned to your application during its creation.
• Click on the "Authentication" button and the following page will appear.

• Paste the [Callback Url] to the Redirect URIs > Add URI text field.
• Paste the [Logout Url] to the Logout URL text field.
• Click on "Save".
  
  

Testing & Activation  

Status
colour Blue title Step 4

The final steps of the initialization of the External Authentication feature, require you to once more go back to the BSS Setup > Administration > System Options > Storefront Login Settings and click on the "Settings (OIDC)" button.

• Click the "Activate" button on the top bar.
• Copy the "Authenticate Url" and open a new web browser tab to paste that URL.
• Your web browser will redirect you to Azure AD in order to log in with your Azure AD credentials.
• After a successful login, you will be redirected back to the Storefront and our system will log in/register you.

By clicking on the "Show Authentication" button from the top bar and the External Authentication will from now on be available to the Storefront.

First Storefront Login with Azure AD Credentials 

After the configuration and activation of the Azure AD external authentication for Storefront, you can choose to login to Storefront via your Azure AD credentials. 

You can click on the "Azure AD" button, located under the External Authentication section.

Provide your corresponding credentials on the new Azure AD login page that you are redirected to or choose one of your "Microsoft Login" saved accounts. 

In the event that your login was not successful, a failure message will appear, as in the following image, indicating the reason.

After a successful login, you are again redirected to our Storefront.

For every first-time login to Storefront via any external identity provider, the following registration form appears once. The registration form is required by our systems in order to properly setup your BSS account as well as your BSS contact, since the external identity provider does not possess all the required information that our systems need.

After filling in all the required fields as well as accepting the "terms of use" check-box and clicking on the "Update" button, a BSS account as well as a BSS contact and a Storefront user are created based on the provided information from the registration form and the Storefront is now fully accessible to you.

As a result, the account and contact that have been created in our BSS are now linked with the Azure AD account used to login to the Storefront.