[GH-ISSUE #5110] Allow configuring OIDC scopes / include groups claim to preserve group mapping #9919

Closed
opened 2026-08-05 01:23:58 -04:00 by saavagebueno · 2 comments
Owner

Originally created by @tilwegener on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5110

Hi NetBird team,

since the update to v0.62.0 it’s now possible to use Simplified IDP which is great. However, with the simplified setup it seems that OIDC scopes cannot be configured.

This becomes a problem for environments where group-based access/mapping relies on the groups claim from the ID token / JWT. In many IdPs, the groups claim is only included when specific scopes are requested (or when explicit group/claim mapping is enabled). With the current simplified flow, we can no longer request the needed scope(s), so the JWT does not contain the groups claim anymore.

Expected behavior

When adding an OIDC provider (even in Simplified IDP mode), admins should be able to:

  • configure the requested scopes (at least optionally), and/or
  • configure/enable group claim delivery (e.g. request group scope / include groups claim)

Actual behavior

  • Simplified IDP does not allow defining scopes
  • JWT/ID token no longer contains the groups claim
  • Group-based mapping/authorization cannot be used

Proposed solution

Add an optional advanced section (or fields) to the OIDC provider configuration that allows:

  • Scopes: e.g. openid profile email groups (customizable)
  • Group claim key (optional): e.g. groups, roles, memberOf
  • (Optional) toggle “Request groups claim / group scope”

This would keep the simplified UX while still supporting enterprise setups that depend on group claims.

Image

Environment

  • NetBird version: v0.62.0
  • Deployment: self-hosted
  • IdP: Pocket-ID

Thanks!

Originally created by @tilwegener on GitHub (Jan 15, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5110 Hi NetBird team, since the update to v0.62.0 it’s now possible to use Simplified IDP which is great. However, with the simplified setup it seems that OIDC scopes cannot be configured. This becomes a problem for environments where group-based access/mapping relies on the groups claim from the ID token / JWT. In many IdPs, the groups claim is only included when specific scopes are requested (or when explicit group/claim mapping is enabled). With the current simplified flow, we can no longer request the needed scope(s), so the JWT does not contain the groups claim anymore. **Expected behavior** When adding an OIDC provider (even in Simplified IDP mode), admins should be able to: - configure the requested scopes (at least optionally), and/or - configure/enable group claim delivery (e.g. request group scope / include groups claim) **Actual behavior** - Simplified IDP does not allow defining scopes - JWT/ID token no longer contains the groups claim - Group-based mapping/authorization cannot be used **Proposed solution** Add an optional advanced section (or fields) to the OIDC provider configuration that allows: - Scopes: e.g. openid profile email groups (customizable) - Group claim key (optional): e.g. groups, roles, memberOf - (Optional) toggle “Request groups claim / group scope” This would keep the simplified UX while still supporting enterprise setups that depend on group claims. <img width="564" height="846" alt="Image" src="https://github.com/user-attachments/assets/14d0d23a-177a-4916-8742-4d7271406ec4" /> **Environment** - NetBird version: v0.62.0 - Deployment: self-hosted - IdP: Pocket-ID Thanks!
saavagebueno added the feature-request label 2026-08-05 01:23:58 -04:00
Author
Owner

@tilwegener commented on GitHub (Jan 17, 2026):

This is already possible for the specific provider Pocket, but it would be good to be able to use it for General OIDC.

<!-- gh-comment-id:3763977512 --> @tilwegener commented on GitHub (Jan 17, 2026): This is already possible for the specific provider Pocket, but it would be good to be able to use it for General OIDC.
Author
Owner

@Jan-Bulthuis commented on GitHub (Mar 26, 2026):

I am now also encountering this issue as my OIDC provider does not seem to provide the groups scope unless requested, could this issue be reopened?

<!-- gh-comment-id:4134268334 --> @Jan-Bulthuis commented on GitHub (Mar 26, 2026): I am now also encountering this issue as my OIDC provider does not seem to provide the groups scope unless requested, could this issue be reopened?
Sign in to join this conversation.
No Label feature-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#9919