Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-19956

LDAPSecMgr uses insecure LDAP even when LDAPS specified

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 6.4.16
    • Fix Version/s: 6.4.22
    • Component/s: LDAP
    • Labels:
      None

      Description

      Even though the admin configured LDAPS on secure port 636, when the ldap security manager starts up it performs an anonymous bind to LDAP/389 in order to query some DC feature support. Should use the configured connect method

        Attachments

          Activity

            People

            • Assignee:
              russwhitehead Russ Whitehead
              Reporter:
              russwhitehead Russ Whitehead
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: