ORCID Misconfirguration

Describe the issue or problem

We updated our Test OJS to the 3.5 LTS version. We copied everything from prod to test. Now when users try to use their ORCID in prod they get missing parameter:redirecr URI.

Steps I took leading up to the issue
We unchecked the ORCID from the test sites as we didn’t want it running for test anyhow.

What application are you using?
For example, OJS 3.5.0.5

Additional information

Hi @sjackson,

This sounds similar to what this user has outlined here (including a solution that worked for them):

Perhaps you could give this a try?

-Roger
PKP Team

Hi Roger and @sjackson:

My posting was an update to an original posting on this issue: ORCID error in OJS 3.5.0.5. I realized that the integration of DOI into the OJS code probably led to the misalignment of ORCID links, which prevented me to authorize my ORCID ID in OJS 3.5. Up to that point, I had been using my person ORCID profile and used the client ID and client secret valued for the journal-level ORCID ID (different from the individual ORCID IDs). By creating a new ORCID profile (for the journal), I replaced my client ID and client secret for the journal with the ones from the new ORCID profile, and that has allowed me to authorize my ORCID ID in OJS 3.5. Mind you: I performed this change in a sandbox installation for 3.5, but if you are working with an institutional ORCID ID for your journal and if you are doing this in a production server, there may be reason for a cautious approach. In such cases, you may be able to switch away from the institutional ORCID ID’s client ID/secret and use yours, and then to switch back again, and try to see of that fixes the ORCID issue on your end. Then try it with someone you know who works with your OJS installation. Advice: backup your directory, database, and whatever customization that you have introduced to your installation.

I hope this helps. Roger @rcgillis has been extremely helpful when answering my postings in the past, so I hope to pay that forward with my modest knowledge of the OJS to help with yours. I would also recommend contacting @piapio who contacted me recently with a similar issue. Perhaps there is something in common with both your issues. All my best! – Arjun Sabharwal @asabhar

Hello,

We have disabled it and the editor says they are still getting messages from users saying the above. This is our test site and we host multiple journals and we have unchecked it from all of them. I just checked our site settings and it’s also unchecked.

It appears somehow when we copied Prod over to test it now redirects to the test site and the credentials are just for PROD. Should I ask them to reenter the credentials into PROD? Or can I do something in the backend?

Thank you for this, it is the journal ORCID ID but the instance it’s trying to activate from is the test. So would reentering the credentials in PROD help? The PROD site is still in 3.3.0-19 and hasn’t been messed with outside of the copy.

Hi @sjackson ,

You would have to enable the ORCID profile plugin in 3.3 and then go to the journal’s website setting and then configure the ORCID plugin. In 3.5 this is different. We use a public API whereas you may be using member. Also, if you are not the admin of the ORCID profile (especially if it is an institutional profile, you may want to work with that person). At any rate, you should back your data up. Best!

@asabhar

The plugin in already on PROD hence why it copied over to the test. We disabled it on test but still the error messages are coming from test saying a redirect. Even disabling it on test it doesn’t seem to do anything but I am waiting to hear back from the journal.

My other step was to change the client ID and secret values in the journal ORCID in the test installation (sandbox, using 3.5). In the PROD (3.3), it used the client ID/secret generated in my own ORCID, but with DOI generation more integrated into the OJS, he original mappings were disrupted. When I created an ORCID just for the journal and used the client ID/secret generated in that profile (to replace the ones inherited from OJS 3.3 during the upgrade), that solved the problem for me. The journal you are working with can also do this: you or they can create a new ORCID profile and swap the secret ID/Client values, and then try to validate some user ORCID IDs.

It has auto switched to mine even being disabled, I am checking with the editor to see if they still get error messages.

It may be the journal manager that yuo may need to speak with unless the journal editor is also the manager.

Is there something in the backend we can try? This seems to be an issue for our whole test and we just don’t want it running on test at all. It doesn’t collect DOIs and doesn’t need the ORCID. However, I’m not sure if it will fix it on the Prod site but it would still help rule the test site out.

I’m sure you already thought about that, but did you check the parameters on the template e-mail? We were having the same issue with only a few journals on a multi-journal installation and it was that.