Task #8469
evaluate if ORCID API will continue to work after 1.2 is deprecated
30%
Description
We use ORCID to authenticate users via OAuth. ORCID has announced that it will completely sunset their version 1.2 API on March 1, 2018 (today). See https://github.com/ORCID/ORCID-Source/blob/master/orcid-model/src/main/resources/README.md The API has been deprecated since early 2017.
We use OAuth portions of the API which do not seem to be affected by the XSD version changes in the ORCID API, but we should evaluate whether this will affect us. In particular, I note that they state that the proper endpoints for OAuth are:
However, for the second of these, our configuration file (https://repository.dataone.org/software/cicore/trunk/d1_portal_servlet/src/main/webapp/WEB-INF/portal.properties) indicates that we use:
I think the pub endpoints have been deprecated, and we may need to change our configuration to use the established endpoint. Evaluate and possibly change this if needed.
Related issues
History
#1 Updated by Jing Tao about 6 years ago
- % Done changed from 0 to 30
- Target version set to CCI-2.3.8
- Status changed from New to In Progress
Matt and Dave discussed the issue a little bit. They think the only change we should make is to change the property orcid.token.location from https://pub.orcid.org/oauth/token to https://orcid.org/oauth/token in the portal.properties file.
I did the change on cn-sandbox. It worked. So I made change on the code on the 2.3 branch as well.
#2 Updated by Dave Vieglais about 6 years ago
- Target version changed from CCI-2.3.8 to CCI-2.3.9
#3 Updated by Rob Nahf about 6 years ago
- Target version changed from CCI-2.3.9 to CCI-2.3.10
2.3.9 is deployed...
#4 Updated by Matthew Jones about 6 years ago
- Related to Task #8533: evaluate and mitigate ORCID OpenId subject change on authentication infrastructure added
