You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Brian Demers (JIRA)" <ji...@apache.org> on 2016/05/25 17:04:13 UTC
[jira] [Updated] (SHIRO-442) CAS client fails with multi-valued
SAML attributes
[ https://issues.apache.org/jira/browse/SHIRO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Demers updated SHIRO-442:
-------------------------------
Fix Version/s: (was: 1.2.5)
1.2.6
> CAS client fails with multi-valued SAML attributes
> --------------------------------------------------
>
> Key: SHIRO-442
> URL: https://issues.apache.org/jira/browse/SHIRO-442
> Project: Shiro
> Issue Type: Bug
> Components: Authorization (access control)
> Affects Versions: 1.2.1
> Reporter: Art O Cathain
> Fix For: 2.0.0, 1.2.6
>
> Attachments: shiro-cas-saml.patch
>
>
> When using org.apache.shiro.cas.CasRealm, if the SAML returned by CAS contains multiple attributes of the same name (e.g. roles?), CasRealm blows up in doGetAuthorizationInfo
> String value = attributes.get(attributeName);
> with
> java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.lang.String
> This is because the org.jasig.cas.client.validation.Saml11TicketValidator is populating the attributes in the
> principal as follows:
> personAttributes.put(samlAttribute.getName(), values.size() == 1 ? values.get(0) : values);
> See attached patch for a fix
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)