CAS + server-side storage of IdP sessions

[Karla Borecky]

Hi everyone,

I wrote recently asking some stupid questions about CAS support by IdP
v3.x. Now I have (I'm hoping) a slightly less stupid question: user session
storage.

I understand that the way these two babies are integrated is by having the
CAS protocols look at the Shib sessions in one shared spot to get their
CAS-y type of auth info. Tickets or whatever. To do this, you have to store
the session info on the Shib server.

But I don't think I knew that this *replaced* the client-side session
storage. Does it eliminate the client session cookies on the client?

Also: if I'm reading correctly: for the simple version of this deployment,
you use the server memory to store all this session info (though you could
set up an actual storage service). I'm wondering how much potential memory
we're talking here. Is there a tool that shows you how many sessions are
out there? Or does anyone have any experience with this?

If you use disk storage for the sessions, does that affect the response
time?

(Starting to feel that this service would have a lot of impact on my IdP
config and so on, for the half dozen people or so who would use it.)

I'm sorry for all the questions. I just want to make sure I understand this
correctly. I appreciate everyone's time.

thanks again,

Karla B

-- 
Karla Borecky
Systems Administrator
ITS
Smith College
Northampton, MA 01063
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160706/9a41add6/attachment.html>