github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2221] Implement OIDC groups claim #6602

New Issue
Open
opened 2026-04-20 17:12:04 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:12:04 -05:00
Owner
Copy Link

Originally created by @winkelement on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2221

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same feature request.

Description

I would be nice to see an implementation of oidc groups claim and scope.

This would enable further implementation of features like automatic group membership and global "whitelist" for specific groups.

Vikunja uses a custom claim vikunja_groups right now which requires customization of the provider which is not always possible.

Using the de-facto standard groups for... well... groups (almost all implementations i encountered use this for group mapping) would enable compatibility with a lot of providers out of the box, for example Google (via dex, this is my usecase).
https://dexidp.io/docs/configuration/custom-scopes-claims-clients/

Which alternatives did you consider using instead?

No response

Originally created by @winkelement on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2221 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same feature request. ### Description I would be nice to see an implementation of oidc `groups` claim and scope. This would enable further implementation of features like automatic group membership and global "whitelist" for specific groups. Vikunja uses a custom claim `vikunja_groups` right now which requires customization of the provider which is not always possible. Using the de-facto standard `groups` for... well... _groups_ (almost all implementations i encountered use this for group mapping) would enable compatibility with a lot of providers out of the box, for example Google (via dex, this is my usecase). https://dexidp.io/docs/configuration/custom-scopes-claims-clients/ ### Which alternatives did you consider using instead? _No response_
GiteaMirror added the area/permissionsarea/auth labels 2026-04-20 17:12:04 -05:00
GiteaMirror commented 2026-04-20 17:12:06 -05:00
Author
Owner
Copy Link

@gabeklavans commented on GitHub (Apr 6, 2026):

My guess is this would be tricky considering it seems that Vikunja relies on the oidcID value in the claim to disambiguate. I'm assuming the values in the groups claim would just be text strings, so Vikunja would have to figure out a way to handle the case where there may be multiple teams with the same name but different internal IDs

<!-- gh-comment-id:4192776421 --> @gabeklavans commented on GitHub (Apr 6, 2026): My guess is this would be tricky considering it seems that Vikunja relies on the oidcID value in the claim to disambiguate. I'm assuming the values in the `groups` claim would just be text strings, so Vikunja would have to figure out a way to handle the case where there may be multiple teams with the same name but different internal IDs
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/auth area/permissions
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6602
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?