Right now, there are three possible authentication methods. Each one of them has its own capabilities and specification. If you are interested in contributing with one more authentication method, please check the guidelines.
JSON Auth (default)
We call it JSON Authentication but it is just the default authentication method and the one that is provided by default if you don't make any changes. It is set by default, but if you've made changes before you can revert to using JSON auth:
1
filebrowser config set --auth.method=json
Copied!
This method can also be extended with reCAPTCHA verification during login:
1
filebrowser config set --auth.method=json \
2
--recaptcha.key site-key \
3
--recaptcha.secret private-key
Copied!
By default, we use Google's reCAPTCHA service. If you live in China, or want to use other provider, you can change the host with the following command:
1
filebrowser config set --recaptcha.host https://recaptcha.net
Copied!
Where https://recaptcha.net is any provider you want.
Note that you always need to set the --auth.method flag when changing authentication configurations and that it will completely overwrite your current settings. This is a known issue.
Proxy Header
If you have a reverse proxy you want to use to login your users, you do it via our proxy authentication method. To configure this method, your proxy must send an HTTP header containing the username of the logged in user:
1
filebrowser config set --auth.method=proxy --auth.header=X-My-Header
Copied!
Where X-My-Header is the HTTP header provided by your proxy with the username.
File Browser will blindly trust the provided header. If the proxy can be bypassed, an attacker could simply attach the header and get admin access.
No Authentication
We also provide a no authentication mechanism for users that want to use File Browser privately such in a home network. By setting this authentication method, the user with id 1 will be used as the default users. Creating more users won't have any effect.