Skip to content

Embedded LDAP SSL should not be enabled when its bundle is empty#50700

Open
leestana01 wants to merge 1 commit into
spring-projects:mainfrom
leestana01:fix-ldap-ssl-empty-bundle
Open

Embedded LDAP SSL should not be enabled when its bundle is empty#50700
leestana01 wants to merge 1 commit into
spring-projects:mainfrom
leestana01:fix-ldap-ssl-empty-bundle

Conversation

@leestana01
Copy link
Copy Markdown

EmbeddedLdapProperties.Ssl.isEnabled() derives enablement from this.bundle != null, so it returns true even when the bundle is overridden to an empty string.

This was harmonized for the other SSL properties classes in #50624 (Cassandra, MongoDB, Redis, Mail), and Couchbase/RabbitMQ already used StringUtils.hasText(...), but EmbeddedLdapProperties was missed. This aligns it with those classes and with its own Javadoc ("Enabled automatically if 'bundle' is provided").

Note: EmbeddedLdapAutoConfiguration additionally guards the bundle with StringUtils.hasLength(...), so this corrects the property's contract rather than changing the end-to-end auto-configuration behaviour.

EmbeddedLdapProperties.Ssl.isEnabled() derived enablement from
this.bundle != null, so it returned true even when the bundle was
overridden to an empty string. Use StringUtils.hasText(this.bundle) to
align with the other SSL properties classes (Cassandra, Couchbase,
MongoDB, Redis, RabbitMQ) and the documented "enabled automatically if
'bundle' is provided" behavior.

Signed-off-by: leestana01 <leestana01@naver.com>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jun 5, 2026
@snicoll snicoll self-assigned this Jun 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: waiting-for-triage An issue we've not yet triaged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants