Dusty, Thanks. I may take you up on the offer even if it is only to see what you did and use it as a starting point. I have one other requirement that I am trying to figure out the best solution for which may impact my needs in as far as CAS goes. I need to be able to maintain a registry (for lack of any better term) of users who are logged in, to which applications they have been logged in, and other information obtained from the client (e.g. the IP address they logged in from) or derived (e.g. the geographical location of the user based on an IP lookup). Since every log in and log out will have to go thru CAS, it seems logical that this 'registry' will need to be either an extension to CAS or a separate application that is tightly integrated with CAS. Obviously, single sign-off will also have to be in this loop.
Thanks for you willingness to share. I will let you know if I decide to take you up on the offer. Bill -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dusty Burwell Sent: Tuesday, June 05, 2007 12:32 PM To: [email protected] Subject: Re: CAS 3.1 Release Bill Bailey <[EMAIL PROTECTED]> writes: > > I am in a similar situation except I am only beginning development. I > have started working with 3.0.7 and was under the impression I might > have to develop my own version of single sign-out, but I would ideally > like to work with the standard version if it is available in time. I > asked the question some time ago when this would be available and I > don't think I ever got any response. I would also be interested in the > answer to this question. > > Bill Bailey > Senior Developer / DBA > Northland, A Church Distributed > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Dusty Burwell > Sent: Tuesday, June 05, 2007 10:37 AM > To: [EMAIL PROTECTED] > Subject: CAS 3.1 Release > > I was wondering if CAS 3.1 was sticking to the roadmap shown here: > > http://www.ja-sig.org/wiki/display/CAS/CAS+3.1+Roadmap > > I've got a project that's using CAS 3.0.7 right now with some > extensions that I made to implement some semblance of single sign out. > But, I'd rather use the standard single sign out provided in version > 3.1 (through SAML?) if possible. > > Even if 3.1 doesn't make the final release date of June 15, if there's > at least a milestone release with the single sign out capabilities > released by then, I'll have time to work with it. If not, then I'll > need to continue with my current implementation (for the time being at > least). > Bill, If it so happens that 3.1 will not be released in time to work with your schedule, I'd be glad to share what I have done for single sign out. It's by far not the most robust implementation and may not work in all cases (I'm not sure how well it works for proxy authentication for instance), but it may be enough to suit your needs for the time being or, at least, a good jumping off point. Dusty Burwell Application Developer Kansas State University _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
