<div dir="ltr"><div><div>Scott and Nate:<br><br></div>Thanks. That was the problem. I'm running Shibboleth 2.2.1. Should have check that first.<br><br></div>Mike<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Mar 17, 2014 at 3:14 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 3/17/14, 2:48 PM, "Michael Dahlberg" <<a href="mailto:dahlberg@bucknell.edu">dahlberg@bucknell.edu</a>> wrote:<br>
><br>
>My first issue is that it seems to be talking about two different<br>
>profiles: SAML2SSOProfile and SAML2ECPProfile. I assumed it meant make<br>
>the changes to the SAML2ECPProfile and I added the following to my<br>
>relying-party.xml file within the DeffaultRelyingParty<br>
> section:<br>
<br>
</div>Well, you'd have to ask them which one they meant.<br>
<div class=""><br>
>which results in a host of java errors. I have not modified the<br>
>handler.xml file and as such there is no SAML2ECPProfile section in that<br>
>file. However, since that file is so rarely modified, I did not think<br>
>that was the root cause.<br>
<br>
</div>Well, you can't make ECP work if it's not defined in handler.xml, but I<br>
don't believe that directly impacts what the profile configuration types<br>
would be, so if the XML is correctly expressed and it's erroring there, I<br>
suspect the IdP is too old to include ECP support.<br>
<br>
-- Scott<br>
<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>
</blockquote></div><br><br clear="all"><br>-- <br>#####################<br>Michael Dahlberg<br>Systems Integrator<br>Bucknell University<br>(570) 577-1595<br>#####################<br>
</div>