06-01-2018 04:09 PM
Have an LXCA server on 1.3.2 that is working with LDAP with no problem. Brought up a new server on 2.0 without migrating anything to it. Went through the initial setup and then set up the LDAP authentication identically to the old one. Literally went through the screens one at a time and mirrored them. Used my own credentials for the binding test, which passed. But when I try to log in with my account I get an error that the username or password isn't valid. I know that's not the case, and my account isn't locked out. The 1.3.2 server is still working with LDAP just fine. Anyone gotten LDAP to work successfully with 2.0?
06-02-2018 03:33 AM
For me it works the same as before. No problem at all.
Did you also remember to create the Role with your AD group name and proper permissions?
Otherwise send screens from the configuration.
06-04-2018 08:51 AM
Yep, used the same group name, made sure it was spelled correctly, has permissions granted to it, etc. If I provide credentials (same ones I'm trying to log in with) and click Apply, I get the success message. Do you happen to be using the Hyper-V VM? Just wondering if there's a possible problem with that specific build.
06-04-2018 12:38 PM
I have vSphere deployment but I doubt that the hypervisor would be the cause.
Never tried with your setup tbh. I always have static AD server configured, works for me either with GC config or standard LDAP port. I also use specific service account to do the login process (bind parameters).
Also, I have filled the root DN to our domain - dc=xx,dc=yy,dc=zzz