<div dir="ltr"><div><div><div><div><div>Hi Peter,<br><br></div>    Yes, it is <a href="http://simplesamlphp.org">simplesamlphp.org</a>, it's part of a Drupal setup.<br><br></div>    What can I advise them?  I've read that simplesaml.php supports SAML2 and I'd thought that was the default.<br><br></div>    Can you recommend any websites or docs I might use to increase my understanding of these concepts?<br><br></div>Thanks<br></div>-Bob<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 19, 2018 at 12:16 PM, Peter Schober <span dir="ltr"><<a href="mailto:peter.schober@univie.ac.at" target="_blank">peter.schober@univie.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">* Robert Lamothe <<a href="mailto:robert_lamothe@yahoo.com">robert_lamothe@yahoo.com</a>> [2018-06-19 17:03]:<br>
> I have an SP that is using Simple SAML<br>
<br>
I only know SimpleSAMLphp, <a href="https://simplesamlphp.org/" rel="noreferrer" target="_blank">https://simplesamlphp.org/</a> are referring to<br>
the same?<br>
<br>
> the request they're sending looks like:<br>
> 20180618T221641Z|urn:mace:<wbr>shibboleth:1.0:profiles:<wbr>AuthnRequest|_2eb287de-083d-<wbr>46b6-a94c-22d7f0295784|https:/<wbr>/<site>/simplesaml/module.php/<wbr>saml/sp/metadata.php/default-<wbr>sp|<a href="http://shibboleth.net/ns/profiles/saml1/sso/browser|https://testshib.umassmed.edu/idp/shibboleth|urn:oasis:names:tc:SAML:1.0:profiles:browser-post|_8c86f56ccf6afcc11b6713b4018da767|svcdrupalldap|urn:oasis:names:tc:SAML:1.0:am:password||AAlzZWNyZXQ4OTBdYyK5C5kwrxXkJHY/UWv7sVFG+W+grJzI4We1r52pSwE4q4hgvlChfr93GbG3Vf1G5fpPo8dr5NY0Lars/454QTzLexdP7Y1IIgqYM2Hn77n2u/7YY3g2V9ugIF6XDzWYqZyouKApz2OdSeZQYpu1xWSmjHzYmAomFzGe3Qsz4Y4eMiOHJEPvUHSYCkBeKXX4roto4GA=|_27827180a700e2846aaa90126dd5dc8d|" rel="noreferrer" target="_blank">http://shibboleth.net/ns/<wbr>profiles/saml1/sso/browser|<wbr>https://testshib.umassmed.edu/<wbr>idp/shibboleth|urn:oasis:<wbr>names:tc:SAML:1.0:profiles:<wbr>browser-post|_<wbr>8c86f56ccf6afcc11b6713b4018da7<wbr>67|svcdrupalldap|urn:oasis:<wbr>names:tc:SAML:1.0:am:password|<wbr>|<wbr>AAlzZWNyZXQ4OTBdYyK5C5kwrxXkJH<wbr>Y/UWv7sVFG+W+<wbr>grJzI4We1r52pSwE4q4hgvlChfr93G<wbr>bG3Vf1G5fpPo8dr5NY0Lars/<wbr>454QTzLexdP7Y1IIgqYM2Hn77n2u/<wbr>7YY3g2V9ugIF6XDzWYqZyouKApz2Od<wbr>SeZQYpu1xWSmjHzYmAomFzGe3Qsz4Y<wbr>4eMiOHJEPvUHSYCkBeKXX4roto4GA=<wbr>|_<wbr>27827180a700e2846aaa90126dd5dc<wbr>8d|</a><br>
<br>
Well, not a SAML request (but the IDP's audit log) but it should<br>
suffice to determine that the SP us using the old, proprietary<br>
Shibboleth-style request for SAML1.<br>
There should be no need to do that, SimpleSAMLphp has support SAML2.0<br>
since the early days.<br>
<br>
> All the other SPs I work with submit HTTP-POST which I believe is default for Shibboleth.<br>
<br>
Not for requests, no. saml2int 0.2 even says the request MUST be using<br>
the HTTP-Redirect prococol binding.<br>
<br>
> I believe this is generated by the SP, but they keep pushing it back<br>
> in my lap.  Is there something I can do on the IDP to insure their<br>
> request is HTTP-POST?<br>
<br>
No, by definition, except you have pre-historic SAML metadata that<br>
doesn't include endpoints with SAML2 bindings.<br>
<span class="HOEnZb"><font color="#888888"><br>
-peter<br>
-- <br>
For Consortium Member technical support, see <a href="https://wiki.shibboleth.net/confluence/x/coFAAg" rel="noreferrer" target="_blank">https://wiki.shibboleth.net/<wbr>confluence/x/coFAAg</a><br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.<wbr>net</a><br>
</font></span></blockquote></div><br></div>