user data is not updated when changed in OIDC IdP.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps are required to reproduce the problem?
- Configure the Dataverse with OIDC authentication.
- Create a new user via OIDC
- Log out via OIDC
- Change email, first name or surname in the OIDC IdP provider
- Login via OIDC, the updated values are not available in Dataverse.
When does this problem occur?
What happens?
Changes to properties within the IdP are not reflected in dataverse.
For whom does it occur (all users, curators, super users)?
All OIDC users.
What did you expect to happen?
The dataverse user data is updated as soon as an OIDC user is authenticated. Even better would be to use the IdP directly to get the information, but updating the information at each login would at least get round the problem.
Which version of Dataverse are you using?
5.13
Are there any open or closed issues related to this bug report?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by tracing the OIDC login flow and the code that creates or retrieves users, then check how email, first name, and surname claims are handled after authentication. Done means changed IdP values are persisted in Dataverse for existing OIDC users after login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100