switch to ORCID Member API about d1_portal_servlet HOT 5 CLOSED

I sent an email to ORCID asking if we can directly transfer our current public API client credentials to the member API, which might be easier than setting up an entire additional registration. I'll respond here if they reply.

from d1_portal_servlet.

@taojing2002 @laurenwalker After some back and forth with the ORCID team, we are now approved to convert our account to the member API. They are looking for a date to do that, as we will need to update our client secret for all clients that use that account, and after they make the change, our app will stop working until we update the secret. When is a good time? In theory the member API should work just like the public API but provide more access. Maybe that needs to be verified before the changeover?

We can now move forward with the migration. Are you able to provide us with a date/time when you would like the migration to happen?

As part of this migration, we will update the client ID and send you a new client secret in an encrypted e-mail. Please note that once we update the client, your integration will not work until you update the client secret. This is why we need to fix a date and time for this to be done and to prevent inconveniences for users.

I will await your response and proceed accordingly.

from d1_portal_servlet.

from d1_portal_servlet.

Hi @taojing2002 I verified with ORCID that, once the conversion is made, then the new Member API will work with our current client ID and our current application. The only thing we will need to update is the client secret. I will coordinate with you on slack to find a time.

from d1_portal_servlet.

The switch was done and Nick recorded the credentials in our password store.

from d1_portal_servlet.