Thanks, Scott.
I have a question related to another response you sent me several months ago. You mentioned the availability of EventHandlers that I might leverage for the purpose of integrating CAS with a presence server (I called it a registry in my last email). You indicated that I could trap events like login, logout, etc. I have found three event types in the JavaDocs for authorization, httprequest, and ticket. But I don't see anything for log outs. Is this something that will have been added as part of the single sign out capability? I'm interested in creating a custom EventHandler that traps on login and logout events and then interacts with my 'registry'. Just to make it a little clearer why I want to do this, we have several places where we want someone to be able to see a real-time list of who is logged into certain applications, where they logged in from, their location (via lookup based on IP), names, addresses, etc. Primarily this is for an online worship center we are developing. Also, I have been able to understand the Events and EventHandlers well enough, but I haven't yet figured out exactly how I go about registering my own EventHandler. Is this just an update to some Spring configuration file? Is there any documentation on doing this or can you give me the quick and dirty description? Thanks for your help and for continuing to support this very useful product. Bill ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Battaglia Sent: Tuesday, June 05, 2007 3:05 PM To: Yale CAS mailing list Subject: Re: CAS 3.1 Release Bill & Dusty, Sorry for the delayed response to your question. I've unfortunately been sidetracked on the CAS release with a few other projects. They've managed to delay milestone releases. I'm hoping to schedule an M3 release for the next two days (probably Thursday). The M3 will technically be feature complete, though I won't call it an RC because I want to have some time to clean up the APIs if necessary. Due to the other projects, the roadmap you guys are referencing is no longer correct. It was rather ambitious ;-). I'll see if I can update it tonight. The M3 release will include the following: * OpenId Support (so you will be able to leverage all OpenId-enabled applications without modifying them). * Google Accounts Integration (for using the Google Apps for Education). * Single Sign Out * Pseudo-anonymous user support. We're still targeting a release candidate by the end of the month, most likely by the time of the conference. A release candidate will be feature-complete and have a frozen API so it is safe to develop against with the knowledge that the final release should be a drop-in replacement. Thanks -Scott On 6/5/07, Bill Bailey <[EMAIL PROTECTED]> wrote: It seems I must apologize. I have searched my old emails once again and I did find where Scott replied to my earlier question about 3.1. Sorry bout that, Scott. In that email, he indicated that they were targeting the end of June so it seems the old date of June 15th for the final release may no longer hold. But he did say that a RC should contain the single sign-off feature and I can only hope that if the final release will be available at the end of June, the RC might be available a few weeks before that. Hope this helps some. 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
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
