docs/content/integration/openid-connect/clients/filebrowser-quantum/index.md
This example makes the following assumptions:
https://filebrowser.{{< sitevar name="domain" nojs="example.com" >}}/https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/filebrowserinsecure_secretSome of the values presented in this guide can automatically be replaced with documentation variables.
{{< sitevar-preferences >}}
The following YAML configuration is an example Authelia client configuration for use with FileBrowser Quantum which will operate with the application example:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- client_id: 'filebrowser'
client_name: 'FileBrowser Quantum'
client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
authorization_policy: 'two_factor'
require_pkce: false
pkce_challenge_method: ''
redirect_uris:
- 'https://filebrowser.{{< sitevar name="domain" nojs="example.com" >}}/api/auth/oidc/callback'
scopes:
- 'openid'
- 'profile'
- 'groups'
- 'email'
response_types:
- 'code'
grant_types:
- 'authorization_code'
access_token_signed_response_alg: 'none'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'client_secret_basic'
To configure FileBrowser Quantum there is one method, using the Configuration File.
auth:
methods:
password:
# Set to false if you only want to allow OIDC.
enabled: true
oidc:
enabled: true
clientId: 'filebrowser'
clientSecret: 'insecure_secret'
issuerUrl: 'https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}'
scopes: 'email openid profile groups'
userIdentifier: 'preferred_username'
disableVerifyTLS: false
logoutRedirectUrl: ''
createUser: true
adminGroup: 'admin'
groupsClaim: 'groups'