Project

General

Profile

Actions

Defect #2210

closed

LDAP authentication source filter causes login to fail

Added by Merul Patel almost 16 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Administration
Target version:
-
Start date:
2008-11-18
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

Downloaded and tested Redmine 0.7.3 on my Mac OS X box (Leopard 10.5.5, stock ruby 1.8.6 patchlevel 114, postgres 8.2.10, and ruby-net-ldap 0.0.4).

All works well, but had issues with getting the LDAP authentication to work. Eventually solved it, but only after doing manual LDAP queries to discover that the LDAP authentication source we use (externally hosted) doesn't specify an 'objectClass' attribute. Consequently, when this filter is applied in the auth_source_ldap.rb file, there are no results from which a distinguished name can be fetched.

Given that the current filter is set to look for all objects with an objectClass attribute of '*' it seems to be the best thing is to remove the object_filter.

Actions #1

Updated by Jean-Baptiste Barth over 11 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

It seems RFC 4512 which defines LDAP standard requires the objectClass special attribute to be present as a way to distinguish object types in the directory. As this issue didn't get more reports, I close it.

Actions

Also available in: Atom PDF