Bill, > 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) >
correct. > > 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. > Good idea. I move it. > 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? > Adding comments to the doc is fine with me, as I receive notifications when someone changes/adds comments. > Regarding release process, perhaps we could use a simple wiki page to > coordinate status, next steps, open issues, etc. > Perfect. Could you please set that up? Best regards, Robert -- 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
