LDAP Security manager should not attempt insecure connection if configured for secure connections

Description

During initialization the security manager attempts to connect to the AD in order to first verify it can connect and to collect some information to determine the AD type. This connection is attempted using the configured protocol (ldap or ldaps). If it fails and is configured for a secure connection, it falls back to an insecure connection. When configured for secure connections, It should never attempt an insecure connection.

Recently some AD connection issues, related to cluster configuration not the LDAP security manager, caused confusion when log entries indicated attempts to make an insecure connection.

In short, when configured for a secure connection, the manager should not attempt an insecure connection.

Conclusion

None

Activity

Show:

HPCC JiraBot August 14, 2024 at 7:36 PM

Jirabot Action Result:
Workflow Transition: Merge Pending
Updated PR

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Priority

Fix versions

Created August 14, 2024 at 1:24 PM
Updated August 21, 2024 at 4:49 PM
Resolved August 21, 2024 at 4:49 PM