davsclaus opened a new pull request, #29321:
URL: https://github.com/apache/camel/pull/29321

   ## Description
   
   [CAMEL-26687](https://issues.apache.org/jira/browse/CAMEL-26687)
   
   The `authenticate` operation of camel-spring-ldap passed the `password` 
entry of the message body to `LdapTemplate.authenticate` as is, so a missing or 
empty password behaved differently depending on the Spring LDAP version and the 
authentication strategy configured on the context source.
   
   - `SpringLdapProducer` now fails the exchange with an 
`org.springframework.ldap.AuthenticationException` when the password is missing 
or empty, before contacting the LDAP server. The check matches Spring LDAP's 
own (`null` or zero length); the exception type is the one Spring LDAP throws, 
so routes see one failure type in every setup.
   - The "Authenticate" section of the component documentation says so (catalog 
copy updated).
   - Tests: `testAuthenticateWithEmptyPassword` and 
`testAuthenticateWithoutPassword` check the exception and that 
`LdapTemplate.authenticate` is never called.
   
   Main only.
   
   ## Target
   
   - [x] I checked that the commit is targeting the correct branch (Camel 4 
uses the `main` branch)
   
   ## Tracking
   
   - [x] If this is a large change, bug fix, or code improvement, I checked 
there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for 
the change (usually before you start working on it).
   
   ## Apache Camel coding standards and style
   
   - [x] I checked that each commit in the pull request has a meaningful 
subject line and body.
   - [x] I have run `mvn clean install -DskipTests` locally from root folder 
and I have committed all auto-generated changes.
   
   _Claude Code on behalf of davsclaus_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_0128ThHB3iQdrvSRLVBGRrdP
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to