Design OIDC flow/integration for builtin Dataverse users #11157
Labels
FY25 Sprint 15
FY25 Sprint 15 (2025-01-15 - 2025-01-29)
FY25 Sprint 16
FY25 Sprint 16 (2025-01-29 - 2025-02-12)
GREI Re-arch
Issues related to the GREI Dataverse rearchitecture
Original size: 80
Size: 30
A percentage of a sprint. 21 hours. (formerly size:33)
SPA.Q1.1
Authentication: OIDC for Builtin users
SPA
These changes are required for the Dataverse SPA
Type: Feature
a feature request
User Role: API User
Makes use of APIs
Overview of the Feature Request
#10959 served as a starting point for the new OIDC-based authentication. This allows users to login to Dataverse from the SPA using OIDC credentials. It also removes our reliance on JSF login and session cookies to access the dataverse API.
Our goal is to support builtin users with OIDC, without affecting the current authentication in JSF. We will analyze the options available, including using Dataverse as an Identity Provider.
This feature will require support from the backend team for analysis and implementation.
What kind of user is the feature intended for?
API User, SPA User
What inspired the request?
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to Dataverse?
Capability for authenticating builtin users using OIDC
Any open or closed issues related to this feature request?
#10959
Are you thinking about creating a pull request for this feature?
Yes
The text was updated successfully, but these errors were encountered: