As of Firefly III 4.7.8 there are two ways to authenticate users. The settings to change these can be accessed through the
.env file in the root directory of your installation, or they can be changed through environment variables (Docker).
If an environment variable itself contains the
= character, you must escape the entire value using quotes:
-e NORMAL_VAR=hello \ -e COMPLEX_VAR="dn=example" \ NORMAL_VAR=hello COMPLEX_VAR="dn=example"
By default Firefly III uses the “eloquent” driver that allows users to register and login locally. This is based on the user’s email address.
Firefly III will allow just one user to register itself after which registration will be blocked. The user who first registered is made administrator and can change the setting over at
/admin to allow others to register.
In the following instructions I will refer to environment variables in all caps, like
To enable LDAP authentication first set
ADLDAP_CONNECTION_SCHEMEto say either
ActiveDirectory, depending on your server.
false. I highly recommend to leave this at
Continue the configuration by changing the following settings:
ADLDAP_CONTROLLERS. A space separated list of LDAP controllers.
ADLDAP_USE_TLSto fine tune the connection. Use
ADLDAP_FOLLOW_REFFERALSif you have multiple LDAP servers that may redirect requests.
ADLDAP_BASEDN to indicate where the users can be located. If necessary, set
ADLDAP_ADMIN_PASSWORD to authenticate towards your LDAP server.
Users type the
ADLDAP_DISCOVER_FIELD into the “User identifier”-box of Firefly III. This could be the distinguishedname, the uid or something else entirely. Firefly III will then use the
ADLDAP_AUTH_FIELD to bind users to itself. The
ADLDAP_SYNC_FIELD finally, will be stored in the user table of Firefly III. My strong suggestion is to keep all of these the same.
If necessary, you can set the following prefixes and suffixes so that the user’s LDAP accounts and the administrator account (optional) are properly formatted for use with your LDAP server:
When you’re feeling especially daring, you can change the following fields to fine tune authentication with Firefly III.
If you set
ADLDAP_PASSWORD_SYNC to true, Firefly III will sync the user’s password to its local user table. This allows users to login to Firefly III when the LDAP server is unavailable. This requires
ADLDAP_LOGIN_FALLBACK to be
true as well.
Generally speaking, Firefly III will give you a “password not accepted” error when something goes wrong. I refer you to the log files of your LDAP server and those of Firefly III to see what went wrong. When in doubt, turn on debug mode and try again.
If you get “cannot be NULL”-errors or “field unavailable”-errors or something like that it means that the discover field, sync field or auth field is empty. Make sure you pick the right field.
The following configuration will allow you to connect to Forum System’s excellent `example LDAP server<http://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/>`_. If you configure your Firefly III system, you can login with user “einstein” with password “password”.
LOGIN_PROVIDER=adldap ADLDAP_CONNECTION_SCHEME=OpenLDAP ADLDAP_AUTO_CONNECT=true ADLDAP_CONTROLLERS=ldap.forumsys.com ADLDAP_PORT=389 ADLDAP_TIMEOUT=5 ADLDAP_BASEDN="dc=example,dc=com" ADLDAP_FOLLOW_REFFERALS=false ADLDAP_USE_SSL=false ADLDAP_USE_TLS=false ADLDAP_ADMIN_USERNAME= ADLDAP_ADMIN_PASSWORD= ADLDAP_ACCOUNT_PREFIX="uid=" ADLDAP_ACCOUNT_SUFFIX=",dc=example,dc=com" ADLDAP_ADMIN_ACCOUNT_PREFIX= ADLDAP_ADMIN_ACCOUNT_SUFFIX= ADLDAP_PASSWORD_SYNC=false ADLDAP_LOGIN_FALLBACK=false ADLDAP_SYNC_FIELD=uid