[Enhancement]: Make the OpenID group claim names configurable #2918

New issue

Closed

opened 2026-02-20 03:02:48 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 03:02:48 -05:00

Owner

Originally created by @yourfate on GitHub (Apr 29, 2025).

Type of Enhancement

Web Interface/Frontend

Describe the Feature/Enhancement

Allow the group names audiobookshelf looks for in the group claim during OIDC to be configured.

Why would this be helpful?

Right now, when I activate the group claim, I have to use the default group names (user, admin, guest).

It would be nice if I could rename those, to something like abs_admins, abs_users etc, without having to use the advanced permissions claim feature. This would also be helpful if I run two different audiobookshelf instances, connected to the same OIDC / LDAP (for example a testing instance without user access).

The current implementation risks that several applications look for admin in the same claim, but I might only grant admin permissions for one of the groups.

I know I could in theory create a 2nd claim just for audiobookshelf groups, but that is annoying in some setups. In mine the groups claim is synced to my OpenID from LDAP.

Future Implementation (Screenshot)

Example from Jellyfin:

Audiobookshelf Server Version

v2.21.0

Current Implementation (Screenshot)

Originally created by @yourfate on GitHub (Apr 29, 2025). ### Type of Enhancement Web Interface/Frontend ### Describe the Feature/Enhancement Allow the group names audiobookshelf looks for in the group claim during OIDC to be configured. ### Why would this be helpful? Right now, when I activate the group claim, I have to use the default group names (`user`, `admin`, `guest`). It would be nice if I could rename those, to something like `abs_admins`, `abs_users` etc, without having to use the advanced permissions claim feature. This would also be helpful if I run two different audiobookshelf instances, connected to the same OIDC / LDAP (for example a testing instance without user access). The current implementation risks that several applications look for `admin` in the same claim, but I might only grant admin permissions for one of the groups. I know I could in theory create a 2nd claim just for audiobookshelf groups, but that is annoying in some setups. In mine the `groups` claim is synced to my OpenID from LDAP. ### Future Implementation (Screenshot) Example from Jellyfin: ![Image](https://github.com/user-attachments/assets/a89b3c51-ad46-4830-ae9c-e542e29611e6) ### Audiobookshelf Server Version v2.21.0 ### Current Implementation (Screenshot) ![Image](https://github.com/user-attachments/assets/e629c114-3dcc-4ed5-8f18-25741fb8b641)

deekerman

2026-02-20 03:02:48 -05:00

closed this issue
added the
enhancement
label

deekerman commented

2026-02-20 03:02:49 -05:00

Author

Owner

@nichwall commented on GitHub (Apr 29, 2025):

Duplicate of https://github.com/advplyr/audiobookshelf/issues/2878

@nichwall commented on GitHub (Apr 29, 2025): Duplicate of https://github.com/advplyr/audiobookshelf/issues/2878

deekerman commented

2026-02-20 03:02:49 -05:00

Author

Owner

@yourfate commented on GitHub (Apr 29, 2025):

Duplicate of #2878

very sorry, didn't find that.

@yourfate commented on GitHub (Apr 29, 2025): > Duplicate of [#2878](https://github.com/advplyr/audiobookshelf/issues/2878) very sorry, didn't find that.

deekerman commented

2026-02-20 03:02:50 -05:00

Author

Owner

@nichwall commented on GitHub (Apr 29, 2025):

No worries

@nichwall commented on GitHub (Apr 29, 2025): No worries