Bug #7066
closed
Unable to bind with DOMAIN\$login any longer
Added by Leah Fisher over 9 years ago.
Updated almost 6 years ago.
Description
When setting the bind account to DOMAIN/$login as the manual suggests for the 1.5 release, it doesn't look like we are translating it any longer into the actual user when logging in.
The log has the following when trying to log in:
Error during authentication: Could not bind to ActiveDirectory user GCITECH\$login
invalid user
I believe in 1.5.2 this error would be the actual user. When looking at the new code, there is nothing about the $login value as there was in the old code. Since I don't have logins working yet with any config, this is all speculation.
- Category set to Authentication
- Target version set to 1.7.5
- translation missing: en.field_release set to 10
- Related to Bug #7003: Unable to connect to AD through ldap login module added
I am able to log in with some changes to the code. Besides having to hardcode the bind user, I needed to update the code to also have the login connect with the domain.
So I did the following:
Account Name: Domain/foreman
Account Password: foreman
Edit line 50 of app/models/auth_sources/auth_source_ldap.rb to:
unless ldap_con.authenticate?("Domain\\#{login}", password)
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
- Target version changed from 1.7.5 to 1.7.4
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/1709 added
- Pull request deleted (
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by