Shibboleth IDP 3 as CAS Server

[Marvin Addison]

>
> But in idp-process.log I get this:
>
> 2015-06-11 14:43:04,759 - INFO
> [net.shibboleth.idp.authn.impl.ValidateUsernamePasswordAgainstLDAP:182] -
> Profile Action ValidateUsernamePasswordAgainstLDAP: Login by 'martinicj'
> succeeded
> 2015-06-11 14:43:04,764 - INFO
> [net.shibboleth.idp.cas.flow.GrantServiceTicketAction:101] - Granted
> service ticket for https://cas.sou.edu/secure/
> 2015-06-11 14:43:04,922 - INFO
> [net.shibboleth.idp.cas.flow.ValidateTicketAction:117] - Successfully
> validated ST-1434058984764-CWnL48dV62jogJ8VXk6F7cVUB for
> https://cas.sou.edu/secure/
>

That simply means that the ticket was found in the backing store. There are
other actions that follow ticket lookup, and judging by the detail code
E_SESSION_EXPIRED, your IdP session could not be found. Are you using a
server-side StorageService implementation for the session store? That's
required since the CAS ticket validation step is a back-channel request and
the default cookie-based store is not suitable in that situation.

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