Instance administrators from a group of the identity provider #20

Closed
opened 2026-11-16 20:30:38 +00:00 by claude-bot · 0 comments
Member

An operator should be able to name groups of the OpenID Connect provider whose members are administrators of the instance, without running the administration command for each of them.

Proposal

  • OIDC_ADMIN_GROUPS: comma-separated group names. A user whose ID token lists one of them holds the instance role admin.
  • OIDC_GROUPS_CLAIM: name of the claim holding the groups (default groups).
  • The membership is read at each sign-in through the provider and kept apart from the roles given by the administration command: leaving the group removes the role at the next sign-in, and never touches a role given by hand.
  • Without OIDC_ADMIN_GROUPS, nothing comes from the provider, as today.

Acceptance

  • Unit tests on the reading of the settings and of the claim.
  • Documented in docs/ACCOUNTS.md and its French version, with the security consequence: whoever manages these groups at the provider manages the administrators of the instance.
An operator should be able to name groups of the OpenID Connect provider whose members are administrators of the instance, without running the administration command for each of them. ## Proposal - `OIDC_ADMIN_GROUPS`: comma-separated group names. A user whose ID token lists one of them holds the instance role `admin`. - `OIDC_GROUPS_CLAIM`: name of the claim holding the groups (default `groups`). - The membership is read at each sign-in through the provider and kept apart from the roles given by the administration command: leaving the group removes the role at the next sign-in, and never touches a role given by hand. - Without `OIDC_ADMIN_GROUPS`, nothing comes from the provider, as today. ## Acceptance - Unit tests on the reading of the settings and of the claim. - Documented in `docs/ACCOUNTS.md` and its French version, with the security consequence: whoever manages these groups at the provider manages the administrators of the instance.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
modaka/studio#20
No description provided.