oscerd opened a new pull request, #23552:
URL: https://github.com/apache/camel/pull/23552
Backports #23506 to \`camel-4.18.x\`.
Cherry-pick of merge commit \`aeb5fd9da\` with the standard 4_21 → 4_18
guide-file adaptation (the original PR's upgrade-guide entry lived in
\`camel-4x-upgrade-guide-4_21.adoc\`, which does not exist on this
maintenance
branch; the same content has been added to
\`camel-4x-upgrade-guide-4_18.adoc\`
instead).
## Summary
Renames the three credential-carrying Exchange header string values in
\`ShiroSecurityConstants\` that drive Shiro authentication to
\`CamelShiroSecurity<Name>\` so they fall under the default
\`HeaderFilterStrategy\` (which strips the \`Camel*\` namespace at transport
boundaries):
| Constant | Previous value | New value |
|----------|----------------|-----------|
| \`ShiroSecurityConstants.SHIRO_SECURITY_TOKEN\` | \`SHIRO_SECURITY_TOKEN\`
| \`CamelShiroSecurityToken\` |
| \`ShiroSecurityConstants.SHIRO_SECURITY_USERNAME\` |
\`SHIRO_SECURITY_USERNAME\` | \`CamelShiroSecurityUsername\` |
| \`ShiroSecurityConstants.SHIRO_SECURITY_PASSWORD\` |
\`SHIRO_SECURITY_PASSWORD\` | \`CamelShiroSecurityPassword\` |
These headers carry credentials and a serialized authentication token, so
filtering them at transport boundaries by default is particularly important.
The Java field names are unchanged so routes referencing the constants
symbolically continue to work; routes using the literal string values must
be updated.
## Test plan
- [x] \`mvn test\` in \`components/camel-shiro\` on 4.18.x — 21 tests pass
- [x] Cherry-pick applied cleanly except for the 4_21 → 4_18 guide-file
rename described above (no merge marker shipped)
- [x] Upgrade-guide entry added under \`=== camel-shiro - potential breaking
change\` in \`camel-4x-upgrade-guide-4_18.adoc\`
Tracker: CAMEL-23577
_Reported by Claude Code on behalf of Andrea Cosentino_
--
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]
