You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2020/08/29 22:08:00 UTC

[jira] [Updated] (ARTEMIS-2889) Support JMS topic use-cases with LegacyLDAPSecuritySettingPlugin

     [ https://issues.apache.org/jira/browse/ARTEMIS-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram updated ARTEMIS-2889:
------------------------------------
    Description: In ActiveMQ 5.x clients with the {{read}} permission can create durable and non-durable topic subscriptions (implemented in Artemis a durable and non-durable queues respectively). However, the LegacyLDAPSecuritySettingPlugin only maps the {{createDurableQueue}}, {{createNonDurableQueue}}, and {{deleteDurableQueue}} permissions to the {{admin}} permission. This should be changed.  (was: In ActiveMQ 5.x clients can create durable and non-durable topic subscriptions with the {{read}} permission. However, the LegacyLDAPSecuritySettingPlugin only maps the {{createDurableQueue}}, {{createNonDurableQueue}}, and {{deleteDurableQueue}} permissions to the {{admin}} permission. This should be changed. )

> Support JMS topic use-cases with LegacyLDAPSecuritySettingPlugin
> ----------------------------------------------------------------
>
>                 Key: ARTEMIS-2889
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2889
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In ActiveMQ 5.x clients with the {{read}} permission can create durable and non-durable topic subscriptions (implemented in Artemis a durable and non-durable queues respectively). However, the LegacyLDAPSecuritySettingPlugin only maps the {{createDurableQueue}}, {{createNonDurableQueue}}, and {{deleteDurableQueue}} permissions to the {{admin}} permission. This should be changed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)