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's app that Shib is using to send the assertion, in order to use an endpoint that's actually saml and not ws-federation, right?<br><br>Thanks,<br><br>On Thursday, January 22, 2015, Cantor, Scott <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> 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, "Thomas Jones" <<a href="javascript:;" onclick="_e(event, 'cvml', 'thomas.jones.g@gmail.com')">thomas.jones.g@gmail.com</a>> wrote:<br>
<br>
<br>
><br>
>I've seen that when my external app sends the respond to Shib's Idp and<br>
>this sends the respond to the ADFS, this one tries to access the next URL<br>
>(but later on it sends the user back to my external app, to repeat the<br>
>authentication process, as I have just<br>
> mentioned):<br>
><br>
><br>
><a href="https://adfs-domain/adfs/ls/?wa=wsignin1.0&wtrealm=https%3a%2f%2appcomain" target="_blank">https://adfs-domain/adfs/ls/?wa=wsignin1.0&wtrealm=https%3a%2f%2appcomain</a>.<br>
>com%2fapp.internet%2f&wfresh=5&wctx=rm%3d0%26id%3dpassive%26ru%3d%252fapp.<br>
>internet%252fHome%252fStart&wct=2015-01-22T00%3a15%3a24Z<br>
<br>
That's WS-Federation, not SAML. Assuming you didn't already know that.<br>
<br>
>But after the user has repeated for the second time the authentication,<br>
>the previous URL is not showed at all. Is this a miss configuration from<br>
>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 href="javascript:;" onclick="_e(event, 'cvml', 'users-unsubscribe@shibboleth.net')">users-unsubscribe@shibboleth.net</a><br>
</blockquote></div>