Shibboleth IDP 3 as CAS Server

[Marvin Addison]

>
> The main requirement for an IdPSession is for tracking an SPSession to
> support SLO, which is an important use case in CAS. I suppose that could be
> made optional, which I recall is what you did in the SAML SSO flows.
>

Nevermind. It's not optional in any way in the current design. I modeled
the CAS protocol ticket-granting ticket (TGT) as the IdPSession object
since it serves exactly the same purpose: its existence is required to
grant a service ticket, it knows the authenticated principal, and it
(optionally) tracks services accessed on it.

M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150612/92998ef4/attachment.html>