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

   Backport to `camel-4.22.x` of #25876, already reviewed and merged on `main`.
   
   - CAMEL-24495: camel-salesforce-maven-plugin - support JWT and Client 
Credentials authentication (#25876, `b4164ad8`)
   
   **Motivation.** Salesforce is retiring the `USERNAME_PASSWORD` grant type in 
Winter '27 (February 2027). The plugin previously only supported 
Username-Password authentication, with the grant type hardcoded in the codegen 
layer. This adds support for the JWT and Client Credentials flows via an 
explicit `authenticationType` parameter, with auto-detection from whichever 
credentials are provided, plus Mojo-level validation that rejects ambiguous 
credential combinations early.
   
   **Not a straight cherry-pick — one conflict, mechanical.** 
`docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_23.adoc` doesn't 
exist on this branch. Per this project's convention, upgrade-guide entries for 
a backported change belong in the matching `camel-4x-upgrade-guide-4_XX.adoc` 
file on `main`, not duplicated onto the maintenance branch — so that hunk is 
dropped here.
   
   **Follow-up needed on `main`:** this backport's fix should get an entry in 
`camel-4x-upgrade-guide-4_22.adoc` on `main` documenting the change for the 
4.22.x line, per the project's backport upgrade-guide policy. Flagging this so 
it isn't missed — not done as part of this PR.
   
   Built and tested `camel-salesforce-codegen` and 
`camel-salesforce-maven-plugin` on this branch, including the new 
`SalesforceMojoValidationTest`.
   
   _Claude Code on behalf of davsclaus_
   
   ## Backport of #25876
   
   **Original PR:** #25876 - CAMEL-24495: camel-salesforce-maven-plugin - 
support JWT and Client Credentials authentication
   **Original author:** @tmielke
   **Target branch:** `camel-4.22.x`


-- 
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