Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3310

LDAP Recursion broken

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Authentication
    • None
    • Debian 10
      Apache mod_auth_kerb
      2016 AD

    Description

      Took me a while to track this down, but it appears a minor tweak to the ldap recursion broke logins for anyone in a nested group, not in the base group.

      Had to add the [0] back in and everything went back to working.

      Against 2019 Domain Controllers, though I'm not sure that matters here as it wouldn't work against older DCs either.

       

      root@observium:/data/observium/html/includes/authentication# diff ldap.inc.php ldap.inc.php.def
      83c83
      < $result = ldap_search_user($element[$config['auth_ldap_attr']['dn']][0], $userdn, $depth);
      —
      > $result = ldap_search_user($element[$config['auth_ldap_attr']['dn']], $userdn, $depth);

      Attachments

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. OBS-3240 Fix for LDAP Web INterface auth

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            [OBS-3310] LDAP Recursion broken
            bot Observium Bot made changes -
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            landy Mike Stupalov made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            landy Mike Stupalov added a comment -

            Please try with r10390.

            landy Mike Stupalov added a comment - Please try with r10390.
            landy Mike Stupalov made changes -
            Status Original: Pending Response [ 10000 ] New: In Progress [ 3 ]
            landy Mike Stupalov made changes -
            Link New: This issue relates to OBS-3240 [ OBS-3240 ]
            landy Mike Stupalov made changes -
            Comment [ Please make and attach additional information about the device:
             * full snmp dump from device:
            {noformat}
            snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
            {noformat}
              _If device not support SNMP version 2c, replace -v2c with -v1._

             * If you have problems with discovery or poller processes, please do and attach these debugs:
            {noformat}
            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>
            {noformat}
             
            * additionally attach device and/or vendor specific MIB files

            {color:#505F79}_Note, this comment is added automatically._{color} ]
            landy Mike Stupalov made changes -
            Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
            arricc Mark McRitchie created issue -

            People

              landy Mike Stupalov
              arricc Mark McRitchie
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: