Specific LDAP configurations are ignored #1

Closed
opened 2024-07-26 09:23:29 +02:00 by Emmanuel BENOîT · 0 comments

While the defaults section of the ldap block is indeed used and works as expected, server-specific settings are ignored. This means that, if no defaults are given, a configuration like this one:

  servers:
    - host: ldap.example.org
      port: 636
      tls: "yes"

will ignore the port and TLS settings, defaulting back to plain LDAP on port 389.

While the `defaults` section of the `ldap` block is indeed used and works as expected, server-specific settings are ignored. This means that, if no defaults are given, a configuration like this one: ```yaml servers: - host: ldap.example.org port: 636 tls: "yes" ``` will ignore the port and TLS settings, defaulting back to plain LDAP on port 389.
Emmanuel BENOîT added the
Kind/Bug
Kind/Security
Priority
Critical
labels 2024-07-26 09:23:29 +02:00
Emmanuel BENOîT self-assigned this 2024-07-26 11:17:44 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: projects/fetchcert#1
No description provided.