[jira] [Updated] (SHIRO-442) CAS client fails with multi-valued SAML attributes

["Brian Demers (JIRA)" <ji...@apache.org>]

     [ 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.3.0)

We talking about moving CAS to the buji-pac4j project for 2.0, and deprecating shiro-cas soon (likely for 1.3)
http://shiro-developer.582600.n2.nabble.com/Future-CAS-module-support-in-Shiro-td7579204.html

If you have thoughts on this, please reply to the above thread.



> 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
>              Labels: patch
>         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)