On 20/10/2011 14:10, Martin Sandiford wrote:
From looking around in the net-ldap code, it looks like one or both of
bind_username and/or bind_password need to be nil for this to happen.
Do you have bind_username and bind_password set up in your production
section of your authentication.yml? Is your server running with the
production environment?
Yes, I'm running in the production environment, and I do have both vars
set with the proper credentials.
I can reproduce this problem if one or both of these config items are
not set --- will improve the behaviour of get_dn_of_user so that it
doesn't fail so catastrophically in this case.
Based on this observation, I set to test with the following ways, and
also compared the results with our redmine install:
bind_username: set
bind_password: set
gitorious: pass
redmine: pass
bind_username: unset
bind_password: set
gitorious: pass
redmine: fail
bind_username: set
bind_password: unset
gitorious: pass
redmine: fail
bind_username: unset
bind_password: unset
gitorious: pass # What? This proves my problem is just with :encryption only
redmine: fail
bind_username: invalid
bind_password: set
gitorious: pass
redmine: fail
bind_username: set
bind_password: invalid
gitorious: pass
redmine: fail
Anyway, this proves that I can authenticate anonymously, but this is not
the case with our Redmine and Chiliproject installation. But whatever it
is I set, it will still fail the authentication test executable. Also,
this, unfortunately, will not indicate if the code to do a binded
authentication is working or not. I know we do have a user in the AD
specifically created just to allow authentications. This was created for
our redmine and apache2/svn authentications.
I'm not sure what's going on with our AD in the office, I do not have
the rights to look into that server.
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
