shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Demers <brian.dem...@gmail.com>
Subject Re: Issue 442
Date Tue, 28 Jun 2016 17:55:10 GMT
Agreed,
I looked at this briefly the other day.  I'm not sure if the patch attached
to the issue will cause a probem when using the CasToken instead instead of
the SAML one.

We need to create a few tests around this.

On Tue, Jun 28, 2016 at 1:43 PM, Daniel M. <dan4bear-tech@yahoo.com.invalid>
wrote:

>
> Would really like to see issue 442 resolved in one of these releases as
> this would help us integrate Shiro in more apps.
> We use CAS and at this point we cannot use shiro to do authorization.
>
> [SHIRO-442] CAS client fails with multi-valued SAML attributes - ASF JIRA
>
> |
> |
> |
> |   |    |
>
>    |
>
>   |
> |
> |   |
> [SHIRO-442] CAS client fails with multi-valued SAML attributes - ASF JIRA
>    |   |
>
>   |
>
>   |
>
>
>

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