+1 -Misagh
> -----Original Message----- > From: Robert Oschwald [mailto:robertoschw...@googlemail.com] > Sent: Thursday, April 04, 2013 9:13 AM > To: cas-dev@lists.jasig.org > Subject: Re: [cas-dev] CAS protocol 3.0 - validation response design > > > > > > <cas:serviceResponse version="3.0" > > xmlns:cas="http://www.yale.edu/tp/cas";> > > <cas:authenticationSuccess> > > > > <cas:authenticationDate>2012-11-16T12:10:23.0Z</cas:authenticationDate > > > > > ... > > > > <cas:proxyGrantingTicket>PGTIOU-84678-8a9d...</cas:proxyGrantingTicket > > > > > <cas:user>username</cas:user> > > <cas:attributes> > > <cas:firstname>John</cas:firstname> > > <cas:lastname>Doe</cas:lastname> > > ... > > </cas:attributes> > > </cas:authenticationSuccess> > > </cas:serviceResponse> > > > > It means that user attributes will be retrieved by existing clients without > modification, but not new authentication attributes (like the > authenticationDate). > > > > I think that it's acceptable as customizations have been made generally to > retrieve user attributes (not authentication attributes). > > > +1 > > As soon as we got a consensus here, I will modify the xsd and sample xml in > the Wip document. > > > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > mmoay...@unicon.net 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
