Purview Sync Application registration issues troubleshooting

In this topic, you can find solutions to common issues when registering the Purview Sync application with Microsoft.

Table of Contents (Advanced Access)

Use this table of contents to navigation Purview Sync during the Advanced Access phase.

Common issues

Click on any of the scenarios to see the cause of the issue and the resolution.

A Microsoft sign-in warning.

Cause

The redirect URI has not been configured. On the Authentication page, in the section Single-page application, the Redirect URIs does not have a configured URI.

Fix

To resolve this issue:

  1. Copy the redirect URI mentioned in error message.
  2. Paste the redirect URI to Single-page application.
    You can also create a URI. For more information, see Register Purview Sync with Azure (Advanced Access)
    The single-page application Redirect URIs in Microsoft.

The single-page application redirect URL with the Relativity URI highlighted.

You can now sign into Microsoft.

Cause

User Client Secret is wrong or expired.

Fix 

Check that you provided Client Secret that is not expired.

To update the client secret,

  1. In RelativityOne, navigate to Purview Sync > Configuration.
  2. If secret is not expired, click Edit. Purview Sync configuration and update Client Secret.
  3. Update the Client Secret field.
  4. Click Save.

For more information see, Creating a client secret

The Client Secret field in the Azure Active Directory Application Registration page.

Cause

Missing Global Admin assigned role.
The Grant admin content for Relativity button on the API permissions page.

Fix

To update the missing Global Admin role,

  1. In Azure, navigate to Users.
  2. Search for your user.
  3. Go to Assigned roles and click link next to the text.
    The Assigned Roles count.
  4. Check if you have Global Administrator role.

It might be that you will see information's about Eligible role assignment. In that case, please contact your Azure administrator.

The Global Administrator role on the Administrative Roles page.

Cause

There is an issue with wrong character in URI. Open Developer tools > Console. Repeat reproduction step to check what is logged in. Console window can look like this
The Console in web developer tools.

Fix

To resolve this issue:

  1. Navigate to Purview Sync > Configuration.
  2. Verify if there is no white spaces at the beginning and end of the URI’s.
    The Azure Active Directory Application Registration fields.
  3. Then navigate to App Registration > Find your application > Authentication.
  4. Verify if Web Redirect URIs and Single-page application Redirect URIs contains correct urls: Web Redirect URIs should contain {Company URI}/purview-sync-services/api/v1/AppConfiguration/auth-response
  5. Single-page application Redirect URIs should contain {Company URI}/Relativity/CustomPages/f444a06a-617c-430b-90b2-a112e834b826/ms-auth-popup-redirect.html Please verify if there are any spaces at the end of beginning of URI.