Prevent logging into a different auth provider when already logged in
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Is it possible to block the login (Built in account login, Shibboleth login ,OAuth Login, ......) when the user has already logined?
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Dataverse User with account
What inspired the request?
The logined users are able to go to the login page and login with another account in Dataverse, and it may confuse users
What existing behavior do you want changed?
The login of Dataverse
Any brand new behavior do you want to add to Dataverse?
Any related open or closed issues to this feature request?
https://groups.google.com/g/dataverse-community/c/Auo_Ih1s6U4
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
The issue names no files, tests, or entry points. Begin by tracing Dataverse's built-in, Shibboleth, and OAuth login flows to determine where an already authenticated user can start another login. Done means an authenticated user is prevented from logging into a different Dataverse account through the login page, with the behavior covered across the relevant providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100