oscerd opened a new pull request, #23506:
URL: https://github.com/apache/camel/pull/23506
## Summary
Renames the three Exchange header string values in `ShiroSecurityConstants`
that drive Shiro authentication (`SHIRO_SECURITY_TOKEN`,
`SHIRO_SECURITY_USERNAME`, `SHIRO_SECURITY_PASSWORD`) to
`CamelShiroSecurity<Name>`, following the convention used across the rest of
the Camel component catalog and matching the pattern established in
CAMEL-23526 (`camel-cxf`), CAMEL-23522 (`camel-mail`), CAMEL-23461
(`camel-aws-bedrock`), CAMEL-23532 (`camel-vertx-websocket` /
`camel-atmosphere-websocket` / `camel-iggy`), and CAMEL-23576 (`camel-jira`).
| 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
(Cluster A — auth/credential/signing exposure — in the CAMEL-23577 epic).
The Java field names are unchanged so routes referencing the constants
symbolically continue to work; routes using the literal string values must
be updated (documented in the 4.21 upgrade guide).
## Generated artifacts
`ShiroSecurityConstants` has no `@Metadata` annotations (this is a
`SecurityPolicy`-style component, not a producer/consumer-style component
that surfaces headers in the catalog), so no catalog JSON or endpoint DSL
regeneration is needed. The diff is exactly the constants file + the upgrade
guide entry.
## Backports
`camel-shiro` exists on `camel-4.18.x` and `camel-4.14.x` with the same
legacy values — backports apply and will be filed as follow-up PRs.
## Test plan
- [x] `mvn test` in `components/camel-shiro` — 21 tests pass
- [x] No literal string usages of these constants in tests or in the shiro
adoc (all references are symbolic via `ShiroSecurityConstants.XXX`)
- [x] Upgrade guide entry added under `=== camel-shiro - potential breaking
change` (consistent with the suffix convention adopted by camel-jira /
camel-jgroups / camel-dns / camel-milo and the in-flight #23505 suffix
follow-up for the other 9 CAMEL-23577 sub-task entries)
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]
