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

Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2022/10/05 08:45:00 UTC

[jira] (ARTEMIS-3984) LegacyLDAPSecuritySettingPlugin shouldn't modify existing matches

    [ https://issues.apache.org/jira/browse/ARTEMIS-3984 ]


    Robbie Gemmell deleted comment on ARTEMIS-3984:
    -----------------------------------------

was (Author: jira-bot):
Commit 2d4e091801e5880380fb65f8c0287ec6317118a8 in activemq-artemis's branch refs/heads/2.21.0.jbossorg-x from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=2d4e091801 ]

ARTEMIS-3984 LegacyLDAPSecuritySettingPlugin shouldn't modify existing matches

When the LegacyLDAPSecuritySettingPlugin has enableListener set to true
and a new permission is added it will try to modify the existing match
if one exists. This is problematic if there's a more generic wildcard
match than the specific one that's modified.

This commit fixes that problem so that instead of modifying the existing
match(es) it simply adds a new one. The plugin never should have tried
modifying the existing match in the first place as two identical matches
would be a configuration error.

(cherry picked from commit a9a85f98db4f49d633541069ae997b4d099837e3)

downstream: ENTMQBR-7118


> LegacyLDAPSecuritySettingPlugin shouldn't modify existing matches
> -----------------------------------------------------------------
>
>                 Key: ARTEMIS-3984
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3984
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.25.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>            Priority: Major
>             Fix For: 2.26.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When the LegacyLDAPSecuritySettingPlugin has {{enableListener}} set to {{true}} and a new permission is added it will try to modify the existing match if one exists. This is problematic if there's a more generic wildcard match than the specific one that's modified.



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