<div dir="ltr">One more thing. In the integration process I didn&#39;t create a specific relying party configuration for this SP, but instead consume their metadata. <div><br></div><div>In their metadata they include the next info:</div><div><br></div><div>....</div><div><div>&lt;SPSSODescriptor WantAssertionsSigned=&quot;true&quot; protocolSupportEnumeration=&quot;urn:oasis:names:tc:SAML:2.0:protocol&quot;&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;KeyDescriptor use=&quot;encryption&quot;&gt;</div><div><span class="" style="white-space:pre">                </span>&lt;KeyInfo xmlns=&quot;<a href="http://www.w3.org/2000/09/xmldsig#">http://www.w3.org/2000/09/xmldsig#</a>&quot;&gt;</div><div><span class="" style="white-space:pre">                        </span>&lt;X509Data&gt;</div><div><span class="" style="white-space:pre">                                </span>&lt;X509Certificate&gt;</div><div><span class="" style="white-space:pre">                                        </span>MII...</div><div><span class="" style="white-space:pre">                                </span>&lt;/X509Certificate&gt;</div><div><span class="" style="white-space:pre">                        </span>&lt;/X509Data&gt;</div><div><span class="" style="white-space:pre">                </span>&lt;/KeyInfo&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;/KeyDescriptor&gt;</div><div><span class="" style="white-space:pre">                </span>&lt;KeyDescriptor use=&quot;signing&quot;&gt;</div><div><span class="" style="white-space:pre">                        </span>&lt;KeyInfo xmlns=&quot;<a href="http://www.w3.org/2000/09/xmldsig#">http://www.w3.org/2000/09/xmldsig#</a>&quot;&gt;</div><div><span class="" style="white-space:pre">                                </span>&lt;X509Data&gt;</div><div><span class="" style="white-space:pre">                                        </span>&lt;X509Certificate&gt;</div><div><span class="" style="white-space:pre">                                                </span>MII...</div><div><span class="" style="white-space:pre">                                        </span>&lt;/X509Certificate&gt;</div><div><span class="" style="white-space:pre">                                </span>&lt;/X509Data&gt;</div><div><span class="" style="white-space:pre">                </span>&lt;/KeyInfo&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;/KeyDescriptor&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;SingleLogoutService Binding=&quot;urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect&quot; Location=&quot;<a href="https://adfs.domain/adfs/ls/">https://adfs.domain/adfs/ls/</a>&quot;/&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;SingleLogoutService Binding=&quot;urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST&quot; Location=&quot;<a href="https://adfs.domain/adfs/ls/">https://adfs.domain/adfs/ls/</a>&quot;/&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;NameIDFormat&gt;</div><div><span class="" style="white-space:pre">                </span>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</div><div><span class="" style="white-space:pre">        </span>&lt;/NameIDFormat&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;NameIDFormat&gt;</div><div><span class="" style="white-space:pre">                </span>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</div><div><span class="" style="white-space:pre">        </span>&lt;/NameIDFormat&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;NameIDFormat&gt;</div><div><span class="" style="white-space:pre">                </span>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</div><div><span class="" style="white-space:pre">        </span>&lt;/NameIDFormat&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;AssertionConsumerService Binding=&quot;urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST&quot; Location=&quot;<a href="https://adfs.domain/adfs/ls/">https://adfs.domain/adfs/ls/</a>&quot; index=&quot;0&quot; isDefault=&quot;true&quot;/&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;AssertionConsumerService Binding=&quot;urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact&quot; Location=&quot;<a href="https://adfs.domain/adfs/ls/">https://adfs.domain/adfs/ls/</a>&quot; index=&quot;1&quot;/&gt;</div><div><span class="" style="white-space:pre">        </span>&lt;AssertionConsumerService Binding=&quot;urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect&quot; Location=&quot;<a href="https://adfs.domain/adfs/ls/">https://adfs.domain/adfs/ls/</a>&quot; index=&quot;2&quot;/&gt;</div><div>&lt;/SPSSODescriptor&gt;</div></div><div>....</div><div><br></div><div><br></div><div>So I&#39;m guessing I&#39;m not using their correct AssertionConsumerService (either POST or redirect) but instead I&#39;m using an endpoint that only understand WS-Federation, right?</div><div><br></div><div>Another question: Why after the Ws-Federation URL is resolved and the end-user reauthenticates, the process is correctly done, I mean the AssertionConsumerService is displayed in the URL address bar and the end-user is send to the Sp&#39;s app?</div><div><br></div><div>Best,</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 22, 2015 at 10:27 AM, Thomas Jones <span dir="ltr">&lt;<a href="mailto:thomas.jones.g@gmail.com" target="_blank">thomas.jones.g@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks Scott for the response.<div><br></div><div>That means that I have to go the ADFS and change the endopoint of the SP&#39;s app that Shib is using to send the assertion, in order to use an endpoint that&#39;s actually saml and not ws-federation, right?<br><br>Thanks,<div><div class="h5"><br><br>On Thursday, January 22, 2015, Cantor, Scott &lt;<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 1/22/15, 2:27 PM, &quot;Thomas Jones&quot; &lt;<a>thomas.jones.g@gmail.com</a>&gt; wrote:<br>
<br>
<br>
&gt;<br>
&gt;I&#39;ve seen that when my external app sends the respond to Shib&#39;s Idp and<br>
&gt;this sends the respond to the ADFS, this one tries to access the next URL<br>
&gt;(but later on it sends the user back to my external app, to repeat the<br>
&gt;authentication process, as I have just<br>
&gt; mentioned):<br>
&gt;<br>
&gt;<br>
&gt;<a href="https://adfs-domain/adfs/ls/?wa=wsignin1.0&amp;wtrealm=https%3a%2f%2appcomain" target="_blank">https://adfs-domain/adfs/ls/?wa=wsignin1.0&amp;wtrealm=https%3a%2f%2appcomain</a>.<br>
&gt;com%2fapp.internet%2f&amp;wfresh=5&amp;wctx=rm%3d0%26id%3dpassive%26ru%3d%252fapp.<br>
&gt;internet%252fHome%252fStart&amp;wct=2015-01-22T00%3a15%3a24Z<br>
<br>
That&#39;s WS-Federation, not SAML. Assuming you didn&#39;t already know that.<br>
<br>
&gt;But after the user has repeated for the second time the authentication,<br>
&gt;the previous URL is not showed at all. Is this a miss configuration from<br>
&gt;the ADFS or Shib?<br>
<br>
Has nothing to do with Shibboleth.<br>
<br>
-- Scott<br>
<br>
--<br>
To unsubscribe from this list send an email to <a>users-unsubscribe@shibboleth.net</a><br>
</blockquote></div></div></div>
</blockquote></div><br></div>