Project

General

Profile

Actions

Defect #1420

open

LDAP authentication extremely flaky

Defect #1420: LDAP authentication extremely flaky

Added by mathew murphy over 18 years ago. Updated almost 14 years ago.

Status:
Needs feedback
Priority:
Normal
Assignee:
-
Category:
LDAP
Resolution:
Affected version:

Description

I hit a problem with LDAP on Linux. It turns out that net/ldap is extremely unreliable when authenticating against the LDAP server at work. I've filed a bug against net/ldap on RubyForge, but since the project seems dormant it's not clear anything will happen.

As a workaround, I coded up a replacement for app/models/auth_source_ldap.rb that uses the Ruby interface to OpenLDAP. So far this has been reliable.

Presumably ruby/ldap works for some people, so it might be nice to offer both as options, but I couldn't immediately work out how to patch RedMine to do that.


Files

auth_source_ldap.rb (4.08 KB) auth_source_ldap.rb Replacement LDAP authentication code using Ruby's OpenLDAP interface mathew murphy, 2008-06-10 19:18
defect_1420_adriano_crestani_rev_2482.patch (5.44 KB) defect_1420_adriano_crestani_rev_2482.patch Patch for revision 2482 Adriano Crestani Campos, 2009-02-20 22:21

Related issues 1 (1 open — 0 closed)

Related to Redmine - Defect #3253: LDAP Auth : Alias DereferenceNewActions

Updated by Adriano Crestani Campos about 18 years ago Actions #1

Hi Mathew,

I also ran into this problem when trying to use the default ldap api on a linux server. Your patch works great, thanks ; )

Adriano Crestani Campos

Updated by Adriano Crestani Campos over 17 years ago Actions #2

I'm uploading a new patch that contains a merge of the file created by Mathew (the one that uses OpenLDAP instead) and the auth_source_ldap.rb file from revision 2482.

Updated by Daniel Marczisovszky over 17 years ago Actions #3

I've created a patch that also uses Ruby/LDAP. After I wrote it, I found your patch and they are very similar ;) However it seems that your patch does not bind as the given user if it is set in the account and password fields. I've (hopefully) fixed it in initialize_ldap_con by adding a call to bind after creating connection. The patch can be found here: #3253

Updated by Antoine Beaupré almost 17 years ago Actions #4

this should be filed under the LDAP category.

Updated by Felix Schäfer almost 17 years ago Actions #5

  • Category changed from Accounts / authentication to LDAP

Updated by Daniel Felix almost 14 years ago Actions #6

  • Status changed from New to Needs feedback

Well maybe this is resolved due some further upgrades of ldap.

Any news on this? Someone who can verify this?

Updated by mathew murphy almost 14 years ago Actions #7

Last time I tried it was when I upgraded to 2.1, and it's still broken there. If there have been LDAP improvements in the last few months, I can try again?

Updated by Daniel Felix almost 14 years ago Actions #8

  • Target version set to Candidate for next major release
Actions

Also available in: PDF Atom