You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2009/12/18 12:17:53 UTC

[jira] Resolved: (AMQ-2508) Activemq should not force third party login modules to use the GroupPrincipal implementation

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

Dejan Bosanac resolved AMQ-2508.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4.0
                   5.3.1

A bit modified patch committed with svn revision 892220. Thanks.

> Activemq should not force third party login modules to use the GroupPrincipal implementation
> --------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2508
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2508
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.3.0
>            Reporter: Giovani Seben
>            Assignee: Dejan Bosanac
>             Fix For: 5.3.1, 5.4.0
>
>         Attachments: AMQ-2508.patch
>
>
> Currently if a third party login module for the broker is written it has to use the implementation of GroupPrincipal from Activemq to create a collection of group objects for an authenticated user. Authorization fails when comparing group objects that are not GroupPrincipal.  This should not be required since any implementation of the java.security.Principal should be sufficient for a group comparison.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.