IQSS / IQSS/dataverse

Feature Request: SPA and JSF logins should invalidate all other logins

Open
#11,814 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

GREI Re-arch SPA Type: Feature
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request When logging in through SPA while already logged into JSF or logging into JSF when already logged in through SPA, OIDC should logout/refresh any existing session. There should be no reason to be logged in as multiple users when switching between different UIs. This can cause issues with logging and security issues may also apply.

What kind of user is the feature intended for? All users other than Guest

What inspired the request? Issues found when sessions were used across UIs

What existing behavior do you want changed? Prevent sharing of session data across UIs

Any brand new behavior do you want to add to Dataverse?

Any open or closed issues related to this feature request? https://github.com/IQSS/dataverse/issues/11519

Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading related issue #11519 and tracing how SPA and JSF logins use OIDC and session data. Define the affected login and logout flows before making changes. Done means switching between the two UIs invalidates or refreshes the existing session so users cannot remain logged in as multiple users.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authentication, backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.