Security group restrictions for OIDC clients #117
Labels
No labels
bug
chore
documentation
enhancement
help
in-progress
question
ready-for-release
released
translation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
adam/gate#117
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Is your feature request related to a problem? Please describe:
Regarding security groups and OIDC, the documentation says "Security Groups are used by OIDC when the OIDC Client requests the 'groups' scope.". However, plenty of apps supporting OIDC make no use of this (for instance, immich), and as such every user has access to these apps.
Describe the solution you'd like:
A way to bind security groups to OIDC clients in a similar way to how it's already handled in proxyauth domains.
Describe alternatives you've considered:
I'm not sure; any way to restrict access for a subset of users to specific OIDC clients in voidauth.
Additional context:
I've been switching over from Authentik, and I'm really liking voidauth and would like to switch over completely. This is really the only feature that I've been missing.
Thank you for opening an issue! 🙂
I will look into adding security groups to OIDC Clients, but there will be significant limitations. VoidAuth would only be able to prevent authorizations to those services when you try to login, not revoke those apps sessions immediately if the user loses access.
Sure, that'd work just fine, for my purposes at least. Thanks!