dataoneorg / d1_portal_servlet Goto Github PK

Current authentication uses the ORCID Public API, and can only access user attributes that are made publicly visible by ORCID users. By switching to the member API, we can then modify our authentication workflow to request additional attributes from the user (such as name, email, institution ,etc) that are not part of their public orcid profile. The user can then grant those requests as a condition of logging into the DataONE authentication portal.

UCSB is an ORCID member and so, after discussion, it seems we can access the member API that way. To get access to the member credentials needed, we will need to fill out the member client registration application, and submit it in conjunction with UCSB using the client registration form.

All of this can be tested ahead of time using the ORCID Sanbox without yet being a member -- see the sandbox client registration FAQ.

The information we will need to provide includes:

• Name of Organization: UC Santa Barbara
• Email of technical contact (technical contact that ORCID has for your organisation):
• Contact for receiving PIN to access credentials: Matt Jones [email protected]
• Name of client application: DataONE
• URL of home page of application: https://dataone.org
• Short description of application: DataONE provides integrated search, discovery and access to data from an international network of repositories.
• Redirect URIs (up to 5):

OAuth 1.0 endpoint is retiring this year on CILogon and all CILogon clients need to migrate to OAuth 2.0 (OpenID Connect) as documented at https://www.cilogon.org/oidc.

When we get the first and last name of the person from the ORCID API, we should also attempt to get the email address and save it to the DataONE account.