Task: Organize Review with ORCID

[mwallschlaeger]

Task Description

make an appointment with ORCID people to show zalf ORCID user management

@EHJ-52n i will let you know when we find an appointment together with ORCID

[mwallschlaeger]

asked for review, we just need to determine if we are rdy and find a date

[mwallschlaeger]

requirements from https://info.orcid.org/documentation/integration-guide/minimum-requirements-for-member-integrations/:

Minimum Requirements for Member Integrations

ORCID members are required to adhere to our integration best practices so that researchers have a consistent experience across platforms. Below is a summary of the minimum our support team will check when reviewing member integrations:

• Collect authenticated ORCID iDs using OAuth.
  • done using keycloak orcid plugin
• Implement OAuth by either:
  Using ORCID as a primary sign in option or
  Using an ORCID Branded button or link to initiate authentication of the iD from within your application
• Use only HTTPS redirect URIs for authentication
• Use relevant scopes for integration – note that you may collect permission from users based on for future integration plans
  Store the Name, ORCID iD and access token from token exchange response
  • we are using: openid, email, profile
• Do not allow users to search or manually enter their ORCID iD
• Do not request users change their visibility settings, or make their email publicly available.
• Display the ORCID iD in accordance with our iD display guidelines
• Use the latest API version
  • depends on keycloak orcid plugin
• Provide an explanation to your users describing the benefits of creating and using an ORCID iD, so they can understand why you are collecting this information and how your integration will benefit them

More details can be found in the integration checklist used by our support team. Our guidance on how to get started building an integration explains how to comply with these best practices

[mwallschlaeger]

@EHJ-52n please check what you think we have accomplished from the minimum requirements of ORCID above

[EHJ-52n]

Implement OAuth by either:

• Using ORCID as a primary sign in option or
• Using an ORCID Branded button or link to initiate authentication of the iD from within your application

The link "ORCID Branded button or link" seems invalid because itis talking about iDs, but not buttons.
Our upload-tool buttons looks like this:

• login:
  
• logout:
  

We are not using the ORCID logo atm, but only the string "ORCID".
The subsections are somehow misleading. We are not implementing oauth with ORCID, but keycloak with orcid extension does it.

Display the ORCID iD in accordance with our iD display guidelines

Needs to be implemented in the nav template and submission overview table in the user column.

Do not allow users to search or manually enter their ORCID iD

When providing author information, the ORIC iD should be entered manually.

Provide an explanation to your users describing the benefits of creating and using an ORCID iD, so they can understand why you are collecting this information and how your integration will benefit them

Is not explizitly done atm. There is some explanation during the "oauth screen to trust the application" (here: application = keycloak).

[mwallschlaeger]

Question to ORCID Consortia:

• how to get affiliation from ORCID response json correct with keycloak response limit of 2k characters?
• Best practice regarding logout from application?