Shibboleth IDP 3 as CAS Server

[Cantor, Scott]

On 6/11/15, 8:22 PM, "Walter Forbes Hoehn (wassa)" <wassa at memphis.edu> 
wrote:



>The CAS protocol support components do, in fact, use the standard 
>attribute filter.  The only catch is that there is no canonical entity 
>ID, so the policy has to reference the URL of the service.  Depending on 
>the CAS client, this might not be fixed per service.  The workaround is 
>to do something like the following:  

Thanks, I was going to follow up and ask so I would know at least 
generally how this works.

-- Scott

>