Robert, Thanks for overview. So the goals for this revision are:
* bring the spec up to date with current Jasig CAS Server behavior * add attributes to CAS payload (a common customization) Does that sound right? Am I missing anything? Given the work currently in flight for CAS4 to make various SAML bits optional, should we move section 2.8 to section 4.x? or at least mark it as optional with a note that this functionality is somewhat superseded by attributes in the CAS response. I have a few more comments on the latest draft....how would you like to receive them? Should I continue to comment on the Google Doc draft? Regarding release process, perhaps we could use a simple wiki page to coordinate status, next steps, open issues, etc. Best, Bill On Mon, Feb 18, 2013 at 1:56 AM, Robert Oschwald <robertoschw...@googlemail.com> wrote: > Bill, > > in the document, every change currently is marked in red. > Here is a brief summary of what was addded: > > - /login parameters "METHOD", "rememberMe", > - /logout parameter "service" with a description of its implication to the > behaviour > - SLO completely added. Also with an on section 4 which briefly describes > the Single Log Out feature and security implications. > - cas attributes in responses > - /proxyValidate added > - /samlValidate added (it is currently in 3.5, which this CAS Spec covers. > In 4.0, this might be removed - to be discussed) > > Open issues: > - JASIG License to be added? This must be checked by one who is into the > license thing. I don't know what the agreement was when Jale donated the spec > and code. > > Robert > > > > Am 16.02.2013 um 00:20 schrieb "William G. Thompson, Jr." <wgt...@gmail.com>: > >> Robert, >> >> This is great news. I'm wondering if could give a brief summary of >> the significant changes/additions/etc to help folks review. >> >> Best, >> Bill >> >> >> On Fri, Feb 15, 2013 at 10:29 AM, Robert Oschwald >> <robertoschw...@googlemail.com> wrote: >>> The 3.0 specification working document on >>> https://docs.google.com/document/d/1l0o60mLfXF4bkQdwRSH4i6P-IJQki3-v-zyoOAjxDd4/edit >>> received some minor changes today. >>> As this specification in my opinion should cover all current (3.5.x) >>> features, I think the main work is done. >>> >>> Could one please bring this document into the formal process to be able to >>> progress to a release version? >>> I'm not sure, but I think it's the steering comitee which releases it, >>> right? >>> >>> After release of 3.0, I recommend to start with 4.0 asap, which covers new >>> features (LOA, FC-SLO, SAML changes, autnN, etc.) >>> >>> >>> Thanks, >>> Robert >>> >>> >>> >>> -- >>> You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@gmail.com >>> To unsubscribe, change settings or access archives, see >>> http://www.ja-sig.org/wiki/display/JSG/cas-dev >>> >> >> -- >> You are currently subscribed to cas-dev@lists.jasig.org as: >> robertoschw...@googlemail.com >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev > > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
