[
https://issues.apache.org/jira/browse/ARTEMIS-6057?focusedWorklogId=1020206&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1020206
]
ASF GitHub Bot logged work on ARTEMIS-6057:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/May/26 09:48
Start Date: 14/May/26 09:48
Worklog Time Spent: 10m
Work Description: gtully commented on PR #6441:
URL: https://github.com/apache/artemis/pull/6441#issuecomment-4449587749
> I'm not sure it is a real use case, however modifying
HierarchicalObjectRepository#addMatch to check both wildcard and FQQN would
prevent wildcard matches for FQQNs.
we can revisit that if ever the security check w.r.t FQQN needs to change,
at the moment it only checks an exact match.
Issue Time Tracking
-------------------
Worklog Id: (was: 1020206)
Time Spent: 50m (was: 40m)
> support literal matches for FQQN security settings, even if they contain
> wildcards
> ----------------------------------------------------------------------------------
>
> 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: 50m
> 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]
