OJS v3 ORCID integration & auto-update

The Redirect URI works as follows:

OJS has a set of addresses it can respond to.

  • OJS production: my public web address is http://ojsPublicAddress
  • OJS development: my restricted web address is: http://ojsPrivateAddress

OJS will append its address onto the OAuth request to ORCID:

  • https://orcid.org/oauth/authorize?response_type=code&client_id=secret&redirect_uri=http://ojsPublicAddress/orcidAuth
    For example, note that here OJS production is telling ORCID to redirect the user back to http://ojsPublicAddress/orcidAuth after successful login.

ORCID has a list of allowed redirect URIs per Client key:

  • permit: http://ojsPublicAddress
  • permit: http://ojsPrivateAddress
  • permit: https://developers.google.com/oauthplayground/
    If ORCID does not recognize the URL is is given in the redirect request, it will not honor the OAuth request.

Hi @ctgraham,

The problem with the Redirect URI was my fault (I edited the previous message, sorry): I forgot to ask ORCID people to add new URI when I decided to test it on our production server. So now I’ve just reproduced the same condition on two different servers: the authorization works, but the accounts are not in sync :frowning:

Has anyone managed to set it up?

Dear ctgraham,

You wrote before: “This ORCID iD is not integrated with ORCID’s new Peer Review3 functionality at this time. You’ve caught my attention with it, however. I’m interested in seeing this integration and will try proposing it within the Pitt ULS for development for 2017. To my understanding, this would require an institutional membership.”

Are there any new developments on this?

Thanks! Gert

Hi @kruger,

I believe you’ve also posted this over here. Please don’t double-post – it clutters the forum.

Regards,
Alec Smecher
Public Knowledge Project Team