Task: Mapping between ORCID Attributes and Application Attributes

[mwallschlaeger]

Task Description

create a mapping overview between ORCID attributes and Geonode/Upload Tool user attributes and groups.

[mwallschlaeger]

Attribute ORCID	GeoNode	Upload Tool	description
ORCID identifier	people.username, people.orcid_identifier	customuser.username
First Name	people.first_name	customuser.first_name	only, if public
Last Name	people.last_name	customuser.last_name	only, if public
email address	people.email	customuser.email	only, if public
Affiliation.name	people.organization.name	[ ]	idk if complex mapping like the onces expected here are possible, this may require extension of GN code
Affiliation.id	people.organization.ror	[ ]
Role/Title	people.position	❌
department	people.department	❌

@silvadealmeida you have a clue on how the fields are names in upload tool?
@EHJ-52n first version

[EHJ-52n]

The mapping of the properties in the upload-tool is done by the allauth socialaccount implementation without any adjustment by us:

[EHJ-52n]

For the upload-tool, we need to decide which properties the user need to provide. Apart from the ORCID id, everything can be hidden and not visible to keycloak and the application.

[EHJ-52n]

In the case of having a public verified email adress, only the approval form is shown and no email entering is required.

[EHJ-52n]

I implemented a first version, which requires additional configuration in the keycloak realm to map the required affilition attribute.
The limitations are:

• only the first affilition is piped into the upload tool
• only data visible to the general public can be seen.
  Setting the level to trusted and being a trusted parties does not enable the application to see the affiliations, name or email.

More complex handling requires the implementation of an keycloak extension, or accessing the ORCID API from within the upload-tool, if the current state is not enough.

See PR https://github.com/zalf-rdm/upload-tool/pull/293 for changes in the upload-tool.

Changes in the keycloak realm will be provided ASAP.

[EHJ-52n]

The documentation of the keycloak realm is updated (see the according commits).

@mwallschlaeger Should I update the realm in identity-e.dataservice.zalf.de, or should we discuss the limitations beforehand?

[mwallschlaeger]

@EHJ-52n please update the keycloak. it is just the test environment so don't hesitate.

[EHJ-52n]

Confgiuration updates are applied.