<div dir="ltr">Hmm, that's what I get for poor copy/paste skills....<div><br></div><div>My _actual_ message in my logs was:</div><div>No profile handler configured for request at path: /Unsolicited/SSO<br></div><div><br>
</div><div>It was missing the SAML2 in the path.</div><div><br></div><div>So my next question should hopefully be quick and easy. </div><div><br></div><div>When it's indicated for /profile/SAML2/Unsolicited/SSO that it needs parameters like providerId, do those params have to be query params or form submitted, or is there flexibility and Shibboleth will be smart enough to extract them?</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 1:00 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 7/25/14, 1:50 PM, "snekse" <<a href="mailto:snekse@gmail.com">snekse@gmail.com</a>> wrote:<br>
<br>
>Related to the IdP-initiated SSO, should I be able to see the<br>
>'/idp/profile/SAML2/Unsolicited/SSO'<br>
> path in my metadata at /idp/profile/Metadata/SAML?<br>
<br>
</div>Nope.<br>
<div class=""><br>
>Wondering because I'm running into the error<br>
>No profile handler configured for request at path: /SAML2/Unsolicited/SSO<br>
<br>
</div>That would normally indicate an older configuration without support for it.<br>
<div class=""><br>
>This is in my handler.xml:<br>
<br>
</div>Then I have no idea. That's all you need.<br>
<div class="HOEnZb"><div class="h5"><br>
-- Scott<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br></div>