> I'm getting conflicting stories on how attributes appear in the CAS response > after a successful login.
I can see why this would be confusing. I ran across the Jira issue that Shi mentioned, and mistakenly thought that the CAS XML protocol had been extended to support attributes. This is not the case. Code review shows the CAS protocol is unchanged; attributes are _not_ transmitted in the service ticket validation response in the CAS 2 protocol (/serviceValidate). See for yourself, http://developer.jasig.org/source/browse/jasigsvn/cas3/tags/cas-3-3-1-final/cas-server-webapp/src/main/webapp/WEB-INF/view/jsp/protocol/2.0/casServiceValidationSuccess.jsp?r=42553. The Jira issue provides a roadmap to _extend_ the CAS 2 protocol to support attribute release. It would be up to you to do this. CAS does support attribute release out of the box. For a while (since 3.3.0?), CAS has supported the SAML 1.1 protocol, which contains <AttributeStatement> elements containing the attributes you configure to release. Example SAML 1.1 payloads containing attributes can be found at http://www.middleware.vt.edu/doku.php?id=middleware:cas:client#sample_saml_responses. Hope that clears things up. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
