<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;">That's one way, but as the IdP wiki documentation states:<div> <a href="https://wiki.shibboleth.net/confluence/display/IDP30/CasProtocolConfiguration" target="_blank">https://wiki.shibboleth.net/confluence/display/IDP30/CasProtocolConfiguration</a><br></div><div><br></div><div>  "Notable features:</div><div><span class="gmail-m_-5944845688281845283Apple-tab-span" style="white-space:pre-wrap">       </span>• The XML response delivered by the /serviceValidate URI includes the <cas:attributes> extension supported by most CAS clients.<br></div></div></blockquote><div><br></div><div>That doesn't really clarify what needs to be configured in attribute-filter.xml or attribute-resolver.xml to facilitate CAS attribute release.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It also supports attribute release via the schema described in the CAS<br>v3 protocol:<br><a href="https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html#head2.5.7" rel="noreferrer" target="_blank">https://apereo.github.io/cas/4.2.x/protocol/CAS-Protocol-Specification.html#head2.5.7</a></blockquote><div><br></div><div>Does the integrated CAS server support support  CAS 2.0 and SAML 1.1 attributes?</div><div>If the CAS SP is included in an active filter policy, are the attributes "just there" on the SP?</div><div><br></div><div>Liam</div></div></div>