1. Yes, we have a dedicated account for LDAP queries. Call it ldapuser
2. BaseDN: ou=users,ou=location,dc=some,dc=company
3. UserDN: cn=ldapuser,ou=users,ou=location,dc=some,dc=company
4. I enabled debugging and tried to log in with my user, which worked before the upgrade, and continues to work on a second Foreman 1.5.1 server. I've verified with my team and all users are experiencing this behavior.
Started POST "/users/login" for x.x.x.x at 2014-09-02 09:04:41 -0700
Processing by UsersController#login as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"oRn6khzmz9DyfcOlNdDZaGyJjFVmS+pQ6KwKuzkvypg=", "login"=>{"login"=>"adminuser", "password"=>"[FILTERED]"}, "commit"=>"Login"}
Setting current user thread-local variable to nil
[[1m[[36mUser Load (1.2ms)^[[0m [[1mSELECT "users".* FROM "users" WHERE "users"."login" = 'adminuser' LIMIT 1[[0m
[[1m[[35mAuthSource Load (1.1ms)^[[0m SELECT "auth_sources".* FROM "auth_sources" WHERE "auth_sources"."id" = 2 LIMIT 1
LDAP-Auth with User adminuser
Result: 49
Message: Invalid Credentials
Failed to authenticate adminuser
Failed to authenticate Admin User against LDAP-Some.Company authentication source
invalid user
Setting current user thread-local variable to nil
Redirected to https://foreman/users/login
Completed 302 Found in 496ms (ActiveRecord: 8.9ms)