Issue with endpoint - "No return endpoint for relying party ...."

[Mark Watson]

Thanks Tom, that ended up being it.

It seems like some identity providers are ok with accepting the
HTTP-Redirect as an AssertionConsumerService as I've gotten unsigned
assertions working using HTTP-Redirect on ADFS.

Appreciate the help!

On Thu, Jan 19, 2017 at 4:33 AM, Tom Scavo <trscavo at gmail.com> wrote:

> On Wed, Jan 18, 2017 at 9:51 PM, Mark Watson <mjw4tson at gmail.com> wrote:
> > I'm having an issue getting my HTTP-Redirect based SP correctly logging
> in...
>
> There is no such thing. HTTP-Redirect is not allowed as an inbound
> binding at the SP. Use HTTP-POST instead.
>
> > edu.internet2.middleware.shibboleth.idp.profile.
> AbstractSAMLProfileHandler:
> > No return endpoint available for relying party ...
>
> Right, your metadata has no AssertionConsumerService endpoint that
> supports the HTTP-POST binding, so the IdP is stuck.
>
> Tom
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170119/a9df1aaa/attachment.html>