shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex White <alexwhite3...@gmail.com>
Subject Re: [jira] [Updated] (SHIRO-442) CAS client fails with multi-valued SAML attributes
Date Sat, 28 May 2016 00:56:12 GMT
unsubscribe

On Thu, Jul 9, 2015 at 5:54 AM, Kalle Korhonen (JIRA) <jira@apache.org>
wrote:

>
>      [
> https://issues.apache.org/jira/browse/SHIRO-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Kalle Korhonen updated SHIRO-442:
> ---------------------------------
>     Fix Version/s:     (was: 1.2.3)
>                    1.2.4
>
> > 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.4
> >
> >         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)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message