OIDC Authentication
Integrate with OpenID Connect providers for single sign-on.
Basic Setup
If you need group claims, add them to scopes (for example groups) per your provider.
Note: Its common to configure a source with denyByDefault and use access rules to enable group based access for OIDC users.
Configuration Options
| Option | Description |
|---|---|
enabled | Enable OIDC authentication |
clientId | OIDC client ID |
clientSecret | OIDC client secret (use env var) |
issuerUrl | OIDC provider URL |
scopes | Requested scopes |
userIdentifier | User field (preferred_username, email, username, phone) |
adminGroup | OIDC group name for admin rights |
userGroups | List of allowed groups (empty = allow all) |
groupsClaim | JSON field for groups (default: groups) |
disableVerifyTLS | Disable TLS verification (testing only!) |
logoutRedirectUrl | Provider logout URL |
Defaults (when omitted): groupsClaim is groups, userIdentifier is preferred_username, and scopes defaults to openid email profile.
Deprecated: createUser in this block is deprecated — omit it; new users are created automatically when OIDC login succeeds.
Issuer URL Examples
Authentik:
| |
Pocket ID/Authelia:
| |
Callback URL
Append /api/auth/oidc/callback to the end of your base URL to get FileBrowser’s OIDC callback URL.
Configure in your OIDC provider:
| |
If you use a custom baseURL in your config.yaml:
| |
Auto-Redirect
When OIDC is the only auth method, users are automatically redirected to the OIDC provider.
Provider Examples
Authentik
Typical settings when Authentik exposes groups and an optional admin group mapping:
Authelia
Minimal Authelia client configuration:
Group-Based Access Control
Admin Group
Grant admin privileges to users in a specific OIDC group:
Restrict login to Specific Groups
Only allow users in specific OIDC groups to access FileBrowser:
Users not in these groups will be denied access even with valid OIDC authentication.