[
https://issues.apache.org/jira/browse/CAMEL-23592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-23592.
--------------------------------------
Resolution: Fixed
> camel-shiro - align Exchange header constant names with Camel naming
> convention
> -------------------------------------------------------------------------------
>
> Key: CAMEL-23592
> URL: https://issues.apache.org/jira/browse/CAMEL-23592
> Project: Camel
> Issue Type: Improvement
> Components: camel-shiro
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.21.0
>
>
> The Shiro security-token constants in
> {{org.apache.camel.component.shiro.security.ShiroSecurityConstants}} use
> string values that do not follow the Camel naming convention:
> * {{SHIRO_SECURITY_USERNAME = "SHIRO_SECURITY_USERNAME"}}
> * {{SHIRO_SECURITY_PASSWORD = "SHIRO_SECURITY_PASSWORD"}}
> * {{SHIRO_SECURITY_TOKEN = "SHIRO_SECURITY_TOKEN"}}
> These are read by {{ShiroSecurityProcessor}} to drive authentication.
> Aligning the string values to {{CamelShiroSecurity*}} matches the default
> {{HeaderFilterStrategy}} namespace and the convention used by sibling
> security components.
> h3. Fix shape
> Rename the *string value* of each producer-read header constant to
> {{CamelShiroSecurity<Name>}}; keep the Java field name unchanged.
> h3. References
> * Tracker: CAMEL-23577
> * Precedent: CAMEL-23526 (camel-cxf)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
