Uploaded image for project: 'Hue (READ ONLY)'
  1. Hue (READ ONLY)
  2. HUE-1182

Handle ldapsearch comments appropriately

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.4.0
    • Component/s: core.users
    • Labels:
      None

      Description

      Sometimes when dealing with Active Directory, an ldapsearch may return extra entries that start with "#". For example:

      dn: CN=Chris Conner,CN=Users,DC=test,DC=com
      objectClass: top
      objectClass: person
      objectClass: organizationalPerson
      objectClass: user
      cn: Chris Conner
      sn: Conner
      givenName: Chris
      distinguishedName: CN=Chris Conner,CN=Users,DC=test,DC=com
      ......

      1. refldap://dev.test.com/DC=dev,DC=test,DC=com
      1. refldap://PROD.test.com/DC=PROD,DC=test,DC=com
      1. refldap://ForestDnsZones.test.com/DC=ForestDnsZones,DC=test,DC=com
      1. refldap://DomainDnsZones.test.com/DC=DomainDnsZones,DC=test,DC=com
      1. refldap://test.com/CN=Configuration,DC=test,DC=com

      Right now we throw a warning message for every entry that we find with the "#". "[11/Apr/2013 15:04:21 +0000] ldap_access WARNING Could not find cn in ldap attributes". Maybe we can change that section to be something like:

      if data[0] != '#':

        Attachments

          Activity

            People

            • Assignee:
              cconner Chris Conner
              Reporter:
              cconner Chris Conner
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: