> I'm thinking that I will have to implement an application-specific user > database, and create a new entry in it for every new authenticated user > that comes down from the container. Kinda hackish, but I don't see > another way.
We have a campus-wide single sign-on thing-- it issues you a cookie, and each page has a tag that checks back against the database to make sure that cookie belongs to that IP address and hasn't expired. Ours is kept under wraps, but I understand from Shawn Bayern that Yale has a similar system and that theirs is open source. Maybe check the Yale website for info, or check with Shawn. I had a link to it at one point but can't find it now. -- Wendy Smoak Applications Systems Analyst, Sr. Arizona State University PA Information Resources Management
