Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design OIDC flow/integration for builtin Dataverse users #11157

Open
GPortas opened this issue Jan 15, 2025 · 0 comments
Open

Design OIDC flow/integration for builtin Dataverse users #11157

GPortas opened this issue Jan 15, 2025 · 0 comments
Assignees
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

Comments

@GPortas
Copy link
Contributor

GPortas commented Jan 15, 2025

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

@GPortas GPortas added Type: Feature a feature request SPA.Q1.1 Authentication: OIDC for Builtin users User Role: API User Makes use of APIs Size: 80 A percentage of a sprint. 56 hours. SPA These changes are required for the Dataverse SPA GREI Re-arch Issues related to the GREI Dataverse rearchitecture labels Jan 15, 2025
@GPortas GPortas moved this to SPRINT READY in IQSS Dataverse Project Jan 15, 2025
@GPortas GPortas moved this from SPRINT READY to This Sprint 🏃‍♀️ 🏃 in IQSS Dataverse Project Jan 15, 2025
@cmbz cmbz added the FY25 Sprint 15 FY25 Sprint 15 (2025-01-15 - 2025-01-29) label Jan 15, 2025
@GPortas GPortas moved this from This Sprint 🏃‍♀️ 🏃 to In Progress 💻 in IQSS Dataverse Project Jan 20, 2025
@GPortas GPortas self-assigned this Jan 20, 2025
@GPortas GPortas added Size: 30 A percentage of a sprint. 21 hours. (formerly size:33) and removed Size: 80 A percentage of a sprint. 56 hours. labels Jan 29, 2025
@cmbz cmbz added the FY25 Sprint 16 FY25 Sprint 16 (2025-01-29 - 2025-02-12) label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Status: In Progress 💻
Development

No branches or pull requests

2 participants