Skip to main content

Troubleshooting M360 Login

Distributor troubleshooting for M360 Azure B2C login to Encompass: wrong site after login, missing Azure login icon, and pre-fetch or authentication errors fixed by reconnecting on the Profile page. v22.02+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 22.02

Steps

Scenario: Azure Login takes the user to a different Encompass Site

  • This occurs when the wholesaler's Redirect URI has not been added to the OAuth configuration in Azure.

  • M360 Support will need to add the Redirect URI, it is not something encompass has access to.

Scenario: Azure login icon is not available on the Encompass Login Page

  • This is more common for new wholesalers

  • Ensure that the URI has been added in M360

  • The settings for Oauth B2C can be set on the Oauth Settings table in Encompass

  • Once this is set, users should be able to log into via AzureB2C and connect their authentication from the Profile page in ECP

Troubleshooting for Pre-Fetch Errors / Authentication Errors:

  1. Have the user logout and log back in to m360 using AzureB2C, if this does not work proceed to step 2

  2. Have the user confirm that their email address on the Encompass user table is identical to the email address setup in Azure

  3. Have the user check the Oauth Authentications table to ensure that there is an authentication available for Azure B2C connected to their authentication. Their authentication ID can be found on the Users table.

  4. If the authentication does not exist, or the token is expired:

  1. Have the user log into ECP

  2. Navigate to their Profile page (this is accessed by clicking on their username@encompassID in the lower right-hand corner of the screen and selecting profile)

  3. There will be an AzureB2C logo to the left of the screen, disconnect this authentication and then reconnect it by clicking the disconnect button and then the connect button.

Did this answer your question?