[BUG] OIDC_ADMIN_CLAIM setting is not honored
Author: Smith8154Created Sep 14, 2026Updated Sep 17, 2026
Labelsfixed in next release
Pre-flight checklist
- I have searched existing issues and this bug has not been reported yet
- I am running the latest available version of TREK
- I have read the Troubleshooting guide and my issue is not covered there
TREK version
4.2.1
Describe the bug
I have set up Authentik as my OIDC provider. I have created a custom entitlement called "trek-admins". I updated my Docker compose and set OIDC_ADMIN_CLAIM=entitlements and OIDC_ADMIN_VALUE=trek-admins. On my next login, my user (the only admin user) had its admin permissions removed. Setting OIDC_ADMIN_CLAIM=groups and OIDC_ADMIN_VALUE=authentik Admins resolves the issue and adds my account back to being an admin.
Steps to reproduce
- Configure
OIDC_ADMIN_CLAIMto be anything other thangroups. - Make sure your user is transmitting whatever claim you are matching on.
- Log in to Trek and you will no longer be an admin.
Expected behavior
I expect Trek to honor the OIDC_ADMIN_CLAIM value.
Deployment method
Other
Host OS
TrueNAS
Accessing TREK from
Desktop browser
Browser (if applicable)
Safari 26.6.2
Relevant logs or error output
Screenshots
No response
Additional context
No response
Source: liketrek/TREK