> <cas:serviceResponse version="3.0" xmlns:cas="http://www.yale.edu/tp/cas";> > <cas:authenticationSuccess> > <cas:authenticationDate>20121116T12:10:23.0Z</cas:authenticationDate> > > <cas:longTermAuthenticationRequestTokenUsed>false</cas:longTermAuthenticationRequestTokenUsed> > <cas:isFromNewLogin>false</cas:isFromNewLogin> > <cas:proxyGrantingTicket>PGTIOU846788a9d...</cas:proxyGrantingTicket> > <cas:user>username</cas:user> > <cas:userAttributes> > <cas:memberOf>ROLE_USER</cas:memberOf> > <cas:memberOf>ROLE_ADMINISTRATOR</cas:memberOf> > <cas:firstname>John</cas:firstname> > <cas:lastname>Doe</cas:lastname> > <cas:title>Mr.</cas:title> > </cas:userAttributes> > </cas:authenticationSuccess> > </cas:serviceResponse>
+1 Simpler, clearer. I don't think we have a use case to make the 3.0 validation response compatible with the 2.0 extensions for attributes. We've seen that XML parsing in some clients is very brittle, so any change is likely a breaking one. Better to simply punt compatibility altogether and define a new endpoint for this response. M -- 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
