feat(server) nt password authentication in ldap backend #4672
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you are using FreeAPI as your ldap backend and two-factor authentication is enabled in FreeAPI, the users will not be able to authenticate using login and password on the Authelia login page when ldap binding is used as an authentication method.
The reason is that two-factor authentication is also used for binding in 389 Directory Server that FreeAPI uses. Depending on the type of two-factor authentication activated in FreeIPA, if it's OTP, then the user must input Password+OTP on the Authelia login page.
The solution is to use the NT Password from user DN instead of trying to check the password by ldap binding.
The PR adds two new configuration options into ldap backend.
authentication_method - takes
bind
ornt_password
. By defaultbind
.nt_password_attribute - has a default value of
ipaNTHash
when implementation is set tofreeipa
.If you decide to accept these changes, perhaps you should improve the documentation I added.