shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Georg Koester (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SHIRO-448) CasRealm not cooperating with other realms: Expects all principals to be originating from itself
Date Sat, 07 Feb 2015 12:59:35 GMT

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

Georg Koester updated SHIRO-448:
--------------------------------
    Summary: CasRealm not cooperating with other realms: Expects all principals to be originating
from itself  (was: CasRealm not cooperating with other realms: Expects all principals to be
originatig from itself)

> CasRealm not cooperating with other realms: Expects all principals to be originating
from itself
> ------------------------------------------------------------------------------------------------
>
>                 Key: SHIRO-448
>                 URL: https://issues.apache.org/jira/browse/SHIRO-448
>             Project: Shiro
>          Issue Type: Bug
>          Components: Realms 
>    Affects Versions: 1.2.0, 1.2.1, 1.2.2
>            Reporter: Georg Koester
>
> in CasRealm.doGetAuthorizationInfo(...):
>         // retrieve user information
>         SimplePrincipalCollection principalCollection = (SimplePrincipalCollection) principals;
>         List<Object> listPrincipals = principalCollection.asList();
>         Map<String, String> attributes = (Map<String, String>) listPrincipals.get(1);
> But if I use multiple realms of course the principal could stem from one of the other
realms and therefore of course be without parameters and causes an IndexOutOfBoundsException
in line 182:
> Map<String, String> attributes = (Map<String, String>) listPrincipals.get(1);
> Workaround: Override doGetAuthorizationInfo in own subclass and fix.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message