You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2026/05/13 09:22:00 UTC
[jira] [Updated] (ARTEMIS-6057) support literal matches for security settings - respect literalMatchMarkers
[ https://issues.apache.org/jira/browse/ARTEMIS-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated ARTEMIS-6057:
--------------------------------
Summary: support literal matches for security settings - respect literalMatchMarkers (was: support literal matches for security settings - literalMatchMarkers)
> support literal matches for security settings - respect literalMatchMarkers
> ---------------------------------------------------------------------------
>
> Key: ARTEMIS-6057
> URL: https://issues.apache.org/jira/browse/ARTEMIS-6057
> Project: Artemis
> Issue Type: Improvement
> Components: Configuration, MQTT
> Affects Versions: 2.53.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
>
> ARTEMIS-4488 introduced literal matches for the address settings, however when configuring security settings using the same
> HierarchicalObjectRepository impl, it is not possible to escape literals. The security repository needs the same capability.
> One use cases is pre configuring a subscriber queue with wildcards and granting consume permissions using a fqqn. It won't work with out support for
> literalMatchMarkers in the security store in the same way as for the address settings HierarchicalObjectRepository
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org