You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/26 20:24:00 UTC

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

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

ASF GitHub Bot logged work on ARTEMIS-3692:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/May/22 20:23
            Start Date: 26/May/22 20:23
    Worklog Time Spent: 10m 
      Work Description: jbertram opened a new pull request, #4099:
URL: https://github.com/apache/activemq-artemis/pull/4099

   This commit includes a handful of changes in order to support using the
   temporary-queue-namespace with security-settings:
   
    - Passing a new temp flag to the SecurityStore implementation.
    - Add plumbing for address-specific operations (e.g. for JMS temporary
   topic use-cases).




Issue Time Tracking
-------------------

            Worklog Id:     (was: 775236)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 10m
>  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.7#820007)