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.

Sign up for GitHub

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

Jump to bottom

Implement OIDC flow/integration for builtin Dataverse users #11197

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

Implement OIDC flow/integration for builtin Dataverse users #11197

GPortas opened this issue Jan 29, 2025 · 0 comments
Assignees
@GPortas
Labels
FY25 Sprint 16 FY25 Sprint 16 (2025-01-29 - 2025-02-12) FY25 Sprint 17 FY25 Sprint 17 (2025-02-12 - 2025-02-26) GREI Re-arch Issues related to the GREI Dataverse rearchitecture Original size: 80 Size: 50 A percentage of a sprint. 35 hours. 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 29, 2025

Overview of the Feature Request

Implementation issue based on the analysis #11157

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)

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
#11157

Are you thinking about creating a pull request for this feature?
Yes
@GPortas GPortas added Type: Feature a feature request 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 Original size: 80 SPA.Q1.1 Authentication: OIDC for Builtin users labels Jan 29, 2025
@GPortas GPortas moved this to SPRINT READY in IQSS Dataverse Project Jan 29, 2025
@GPortas GPortas moved this from SPRINT READY to This Sprint 🏃‍♀️ 🏃 in IQSS Dataverse Project Jan 29, 2025
@GPortas GPortas added the FY25 Sprint 16 FY25 Sprint 16 (2025-01-29 - 2025-02-12) label Jan 29, 2025
@GPortas GPortas self-assigned this Feb 5, 2025
@GPortas GPortas moved this from This Sprint 🏃‍♀️ 🏃 to In Progress 💻 in IQSS Dataverse Project Feb 10, 2025
@GPortas GPortas added Size: 50 A percentage of a sprint. 35 hours. and removed Size: 80 A percentage of a sprint. 56 hours. labels Feb 12, 2025
@cmbz cmbz added the FY25 Sprint 17 FY25 Sprint 17 (2025-02-12 - 2025-02-26) label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GPortas GPortas

Labels
FY25 Sprint 16 FY25 Sprint 16 (2025-01-29 - 2025-02-12) FY25 Sprint 17 FY25 Sprint 17 (2025-02-12 - 2025-02-26) GREI Re-arch Issues related to the GREI Dataverse rearchitecture Original size: 80 Size: 50 A percentage of a sprint. 35 hours. 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
IQSS Dataverse Project
Status: In Progress 💻
Milestone
No milestone
Development

No branches or pull requests
2 participants
@GPortas @cmbz