You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By switching to the ORCID member API, we can make attribute requests during the authentication process by asking for information only accessible to trusted organizations.
This allows us to ask for a user's email address, even if it has been set to trusted (whereas now we only see the user's public address). This will allow us to ensure that we have a valid email address for all logins.
If a user has set their email to 'only me' in their ORCID profile, then we should deny the login and indicate that they need to make their email available to trusted orgs for login to work.
By switching to the ORCID member API, we can make attribute requests during the authentication process by asking for information only accessible to trusted organizations.
This allows us to ask for a user's email address, even if it has been set to trusted (whereas now we only see the user's public address). This will allow us to ensure that we have a valid email address for all logins.
If a user has set their email to 'only me' in their ORCID profile, then we should deny the login and indicate that they need to make their email available to trusted orgs for login to work.
See: https://support.orcid.org/hc/en-us/articles/360006897614
Also see semi-related Issue: #2
The text was updated successfully, but these errors were encountered: