activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-904) SecurityContext doesn't work with WebLogic Principals
Date Fri, 08 Jul 2011 20:59:16 GMT

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

Timothy Bish closed AMQ-904.
----------------------------

    Resolution: Not A Problem

Doesn't appear to be applicable to the current codebase.  

> SecurityContext doesn't work with WebLogic Principals
> -----------------------------------------------------
>
>                 Key: AMQ-904
>                 URL: https://issues.apache.org/jira/browse/AMQ-904
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.0.1
>            Reporter: Aaron Mulder
>             Fix For: NEEDS_REVIEWED
>
>
> SecurityContext.isInOneOf attempts to determine whether a user has one of a set of possible
principals.  It does this by using HashSet.retainAll, which relies on equals and hashcode.
> This doesn't work for WebLogic principals (the variable "set" in that method always ends
up empty).  I'm not totally clear on why, but I notice that the principals generated by a
WebLogic authentication have signature data, while the principals created as the "eligible
principals" using the same WebLogic classes (weblogic.security.principal.WLSGroupImpl) have
null signature data.  I speculate that WebLogic signs the principals it creates and that equals
and/or hashCode consider the signature.
> It would be ideal if SecurityContext.isInOneOf manually compared the principal class
and principal name instead of relying on the equals and/or hashCode methods of the underlying
principal class.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message