Content
You are here:
LDAP Authentication: OP doesn't try to authenticate user against LDAP/AD
Added by Stephan Budach over 1 year ago
I am trying to configure OP community edition (for now) to authenticate against our AD. I have created a LDAP Authentication object and the connection check reports success. Then I set my user account to use this LDAP authentication, but upon trying to log in, my credentials can't be verified.
It looks like OP isn't even trying to authenticate my account, since I can't find any login attempts on our AD for that. I then tried an incorrect password for my AD user, since we do have a lockout policy which will temporarily disable an account if repeated failed logins occur, but that wasn't invoked as well.
Is there some option to dig deeper into the logs? There must be something amiss.
Replies (3)
Well, yes - I did that and I already tried it twice. I even set up a new instance, but the result is the same. OP does connect to the LDAP server using the configured AD user. It also fetches my avatar from AD, but it doesn't authenticate me. On my LDAP server, I can't find any hints to an attempted LDAP bind for my user.
Hence the question, if there's an option to see whether OP actually tries to authenticate my account via AD, or if it fails on local authentication, which is not set for this account. I set "Authentication mode" to the LDAP authentication name, I have set up.
Ahh… never mind. I traced the authentication with tcpdump and noticed a type for the user name attribute mapping. Fixed that and off we go.