ORCID integration - redirect URIsORCID integration - redirect URIs

What 

When using Pures integration with ORCID, your Pure users are required to authorise Pure read/write permissions to their ORCID profile. 

The authorisation process starts inside Pure on the personal users workspace. Here the user is being directed over to ORCID for authorising read/write permissions, and then ORCID redirects the user back to his/her Pure workspace for completing the authorisation. 

ORCID can only send the user back to Pure if the redirect URI to Pure Admin is configured on the Institutions Client ID account. If the redirect URI is not correct/not configured, ORCID will show an error message saying the redirect URI is not correct, so it cannot bring the user back to Pure for completing the authorisation process inside Pure:

How 

If your users get a redirect URI error message from ORCID. 

The error message is related to what you have registered on the ORCID side. You will need to provide the correct URI on your Institutions ORCID Client ID account at ORCID.org. 

Check your account/client ID (the ID number is the one shown in the redirect URI error message from ORCID), and make sure that you registered at the /admin subdomain URL to Pure as the redirect URI:

www.(insert your pure url)/admin

example: www.testuniversity.elsevierpure.com/admin 

More information

Redirect URIs are part of the registration process you did in ORCID to get a public or a member API client account and credentials for your Pure integration with ORCID. 
About redirect URIs in ORCID: https://info.orcid.org/ufaqs/how-do-redirect-uris-work/

If in doubt try contact ORCID Support for assistance.