[
https://issues.apache.org/jira/browse/ARTEMIS-6057?focusedWorklogId=1020063&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1020063
]
ASF GitHub Bot logged work on ARTEMIS-6057:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 13/May/26 15:28
Start Date: 13/May/26 15:28
Worklog Time Spent: 10m
Work Description: gtully commented on PR #6441:
URL: https://github.com/apache/artemis/pull/6441#issuecomment-4442611550
@jbertram should I consider combining the exact and literal match maps?
Issue Time Tracking
-------------------
Worklog Id: (was: 1020063)
Time Spent: 20m (was: 10m)
> 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
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
