security
Proxy Authentication
Authenticate based on HTTP headers – strictly designed to be used behind a reverse proxy.
Configuration
If proxy authentication is enabled and a server is accessed without a proxy, FileBrowser will blindly accept the headers. If anyone can bypass the proxy, they can login as any proxy-based user. Take care to configure your environment securely when using this method.
| |
Options
| Option | Description |
|---|---|
enabled | Enable proxy authentication |
header | Required. Header whose value is trusted as the username (must sit behind a trusted proxy) |
adminGroup | Group name that grants admin (if your proxy/IdP also sends group claims — integration-dependent) |
userGroups | If set, only users in these groups may log in |
groupsClaim | JSON field name for groups when reading group data (default: groups) |
userIdentifier | Field to use as username when not using the raw header value in composite setups |
disableVerifyTLS | Disable TLS verification for any outbound calls (testing only) |
logoutRedirectUrl | Optional URL to redirect after logout |
Deprecated: createUser in this block is deprecated and ignored for new configs — user provisioning behavior is always on for supported methods.
Example Use Cases
- Corporate SSO via proxy
- Kubernetes ingress authentication
- Nginx auth_request module
- Traefik ForwardAuth
Traefik Example
Nginx Example
| |
FileBrowser config: