Hi Chris,
On Wed, Mar 16, 2016 at 7:12 AM, Chris Murphy
<
chrismich...@gmail.com> wrote:
> ldapsearch -h
users.forms.com -p 389 -x -D
> "uid=123456,c=ie,ou=users,o=
forms.com" -b "
ch...@ie.forms.com" -W
> Enter ldap password : 123456
> Found Email
>
> Changes this over to vault write to try and bind a user and password
> vault write auth/ldap/config url="ldap://
users.forms.com:389" userattr=mail
> userdn="ou=users,o=
forms.com" binddn="uid=123456,c=ie,ou=users,o=
forms.com"
> bindpass="123456" insecure_tls=false starttls=true
In your ldapsearch command you are not using TLS, but you have
'starttls=true' set in your Vault config. This could certainly cause a
timeout problem, if Vault is waiting expecting to establish a TLS
session.
Any chance you can get ldapsearch to spit out more details about the
found user? In Vault, once there is a successful bind with a set bind
DN/bind password, it does a subtree search under the user DN with a
filter of (in your case) '(mail=
ch...@ie.forms.com)'. The value that
is returned is passed verbatim into authentication. It'd be nice to
verify from ldapsearch that your user DN is correct and that this
constructed DN from the search is what is expected.
Thanks,
Jeff