Relinking only changes the token but not the orcid id on the dockstore profile

Describe the bug Relinking only changes the token but not the orcid id on the dockstore profile

Exporting a workflow to ORCID using https://dev.dockstore.net/api/static/swagger-ui/index.html#/entries/exportToORCID fails if Relink ORCID Account is clicked and the original ORCID account is no longer present.

Error message is something like: Could not export to ORCID. {"response-code":"401","developer-message":"401 Unauthorized: The client application is not authorized for this ORCID record. Full validation error: Access token is for a different record","user-message":"The client application is not authorized.","error-code":"9017","more-info":"https://members.orcid.org/api/resources/troubleshooting"}

To Reproduce Create an account on sandbox.orcid.org (you will need to add a mailinator.com email address, e.g. [e-mail], to verify the account at mailinator.com. Link to the sandbox.orcid.org account on your Dockstore Accounts page Create another account on sandbox.orcid.org Go to the new ORCID account on sandbox.orcid.org Account page Click on Remove duplicate record and merge the first sandbox.orcid.org account in the new account

On the Dockstore Accounts page click ‘Relink ORCID Account’

Create a DOI for a workflow Export the workflow to ORCID using https://dev.dockstore.net/api/static/swagger-ui/index.html#/entries/exportToORCID

See error above

Expected behavior A dialog should ask you to login to the new ORCID account

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Device: Mac
• OS: Big Sur 11.2.3 (20D91)
• Browser Chrome
• Version Version 89.0.4389.114 (Official Build) (x86_64)

Additional context

• UI version:
• Webservice version: [e.g. 1.8.0]
• host location: dev.dockstore.org

Webservice

• 45e63c0

UI

• 2.7.3-92-gd412ffc8

Compose Setup

• 80a6669

Deploy

• 1.10-70-g803c792

┆Issue is synchronized with this Jira Story ┆fixVersions: Dockstore 1.13 ┆friendlyId: DOCK-1790 ┆sprint: 95- W ┆taskType: Story

[coverbeck]

Reading up on it, this is a really extreme case. ORCID is designed to discourage more than one account for an individual. That same page has a proviso for removing a duplicate account though, but I don’t think you can’t actually “transfer” your data between accounts. In thise Dockstore ends up with a putCode that refers to a record that’s been deleted…

I’ll add something to the FAQ; just noting this.

Also, looking at the code, I’m not sure we should be storing the putCode in the first place. It seems like we could get it dynamically. But that’s another issue.

[unito-bot]

➤ Kathy Tran commented:

PR: https://github.com/dockstore/dockstore-documentation/pull/220 ( https://github.com/dockstore/dockstore-documentation/pull/220|smart-link )

Verified that this FAQ entry exists in our docs: https://docs.dockstore.org/en/stable/faq.html#what-happens-if-i-link-to-a-different-orcid-account ( https://docs.dockstore.org/en/stable/faq.html#what-happens-if-i-link-to-a-different-orcid-account|smart-link )

Moving to Done