Shibboleth Developers

[Scott Cantor <>]

> So the question (IMHO) with mysql is:  is it likely enough to 
> be of value to most targets that it's worth the pain of 
> getting it to work or switching to some other method.  My 
> feeling is that the average target won't need stored-on-disk 
> session info (how many have it now?), and would find a mysql 
> dependency just another bump to get over.

Well, the binary has no additional dependencies (you don't have to install
mysql to use it). If that weren't the case, I would have been against even
using it. It is one more source dependency, though it just takes two seconds
to change the configuration file to bypass it. Nobody would remember though.

The other thing is that the build on Solaris isn't clean, because they have
bugs in their build (which I don't quite get, but anyway...) So it's a
hassle in that sense.

I actually do have persistent sessions here, in the sense that before I had
them, if my web server bounced, I'd lose them, and that wasn't acceptable
given that I had crash problems and because Apache by its nature couldn't
use a non-persistent cache.

With the shar, you don't have those issues, so if the shar stays up, you're
ok. That's the only reason I see it as less critical, esp. since so much of
the config now is dynamic.

So a reasonable question might be, should we enable it in the binary we ship
but not in the source? That's not automatic right now because we blindly
copy the config file over during builds, but I could certainly do it.

-- Scott

------------------------------------------------------mace-shib-design-+
For list utilities, archives, subscribe, unsubscribe, etc. please visit the
ListProc web interface at 

    http://archives.internet2.edu/

------------------------------------------------------mace-shib-design--