You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Vadzim (Jira)" <ji...@apache.org> on 2022/09/09 06:40:00 UTC

[jira] [Commented] (ARTEMIS-3692) Extend Functionality of Temporary Queue Namespace to Security Settings

    [ https://issues.apache.org/jira/browse/ARTEMIS-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602147#comment-17602147 ] 

Vadzim commented on ARTEMIS-3692:
---------------------------------

Can I kindly ask about the status of MR? Is there any blockers?
As per ARTEMIS-3974 we have security hole in the configuration.
Thanks in advance.

> Extend Functionality of Temporary Queue Namespace to Security Settings
> ----------------------------------------------------------------------
>
>                 Key: ARTEMIS-3692
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3692
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Kevin O'Neal
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Currently the temporary-queue-namespace is only relevant for address-settings, not security-settings. Therefore, the only way to enforce security settings on temporary queues is to use the match "#".



--
This message was sent by Atlassian Jira
(v8.20.10#820010)