Am I misremembering that in CAS protocol v2, /serviceValidate did not return attributes – that basically it was an update to CAS1 /validate using an XML response? If you wanted attributes, in CAS2, you had to use /samlValidate and got a SAML1.1 response? And CAS3 introduced /p3/serviceValidate to provide attributes in its native CAS XML schema?The current documentation for the CAS3 protocol is perhaps(?) confusing. Section 2.5.5 references CAS3, and the example responses in 2.5.7 include attributes. But the example URLs in 2.5.6 do not include /p3 in the path. E.g. "https://cas.example.org/cas/serviceValidate?...". Later in 2.8--Baron Fujimoto <ba...@hawaii.edu> ::: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum descendus pantorum