After #30 is merged, we are facing a health check issue for LDAP.
By default, if Spring LDAP implementation is present, healthcheck attempts to include it into the checking (fails is LDAP connection fails). Currently, this default behavior is disabled in config in by management.health.ldap.enabled=false.
When enabled, just as-is, the user is presented with:
org.springframework.ldap.CommunicationException: localhost:389; nested exception is javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]
Please find a working setup, but consider the ability to set different modes authorization, too (as outlined in #28).
Hints: maybe we are missing config entries in spring.ldap.* (src) or we are missing a dependency org.springframework.ldap:spring-ldap-core (src). Or maybe both.
After #30 is merged, we are facing a health check issue for LDAP.
By default, if Spring LDAP implementation is present, healthcheck attempts to include it into the checking (fails is LDAP connection fails). Currently, this default behavior is disabled in config in by
management.health.ldap.enabled=false.When enabled, just as-is, the user is presented with:
Please find a working setup, but consider the ability to set different modes authorization, too (as outlined in #28).
Hints: maybe we are missing config entries in
spring.ldap.*(src) or we are missing a dependencyorg.springframework.ldap:spring-ldap-core(src). Or maybe both.