<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><style type="text/css">p { margin: 0; }</style></head><body><div>Hi Andrew,</div><div><br></div><div>I think I encountered what you're referring to recently myself. For SAML1 you need to configure back-channel support for that as well:</div><div><br></div><div><a href="https://wiki.shibboleth.net/confluence/display/IDP30/Jetty9#Jetty9-SupportingSOAPEndpoints">https://wiki.shibboleth.net/confluence/display/IDP30/Jetty9#Jetty9-SupportingSOAPEndpoints</a></div><div><br></div><div>Thanks,</div><div><br></div><div><br class="Apple-interchange-newline"><span style="font-family: monospace; white-space: pre;">--
Brandon McKean
IT / Systems
Linux Administrator
(540)568-4235</span></div><div><br></div><div>On Mon, 2015-07-20 at 09:28 -0400, Andrew Chiarello wrote:</div><blockquote type="cite"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000">Hi,<br><br>I'm still fairly new to Shib, and I believe I have a configuration mistake, but I'm not quite sure where to look. What I'm seeing is that while attributes are being released normally when a SAML2 request comes in, no attributes are being sent for SAML1 requests. Can someone point me in the right direction to investigate that?<br><br><div><span name="x"></span><br>Andrew J. Chiarello <br>Network & Systems Engineer<br>Bryn Mawr College <br>610-526-7966 <br>achiarello@brynmawr.edu <span name="x"></span><br></div></div><pre>--
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a></pre></blockquote></body></html>