You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shiro.apache.org by "Daniel M." <da...@yahoo.com.INVALID> on 2016/06/28 17:43:30 UTC

Issue 442

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
   |   |

  |

  |

Re: Issue 442

Posted by Brian Demers <br...@gmail.com>.

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. <da...@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
>    |   |
>
>   |
>
>   |
>
>
>