Failed LogoutRequest with "No SAMLBindingContext or binding URI available" error reported by Shib

[Wayne Si]

Thank you very much Scott. I sensed the same initially but gave up quickly after a fruitless search. But your confirmation forced me to do more research in this direction and yes, it is the cause.

For the achieve, the SP needs to implement a callback URL to receive the logout response from the IdP and this URL must be provided in the SP's metadata in a SingleLogoutService tag.

Wayne

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: 29 July 2015 15:37
To: Shib Users <users at shibboleth.net>
Subject: Re: Failed LogoutRequest with "No SAMLBindingContext or binding URI available" error reported by Shib

On 7/29/15, 9:15 AM, "users on behalf of Wayne Si" <users-bounces at shibboleth.net on behalf of w.si at celcat.com> wrote:



>My code can successfully log into my SP through the Shibboleth IdP. But when I tried to logout by sending a LogoutRequest to the IdP, I ended up with the Shibboleth error page saying “The login service was unable to identify a compatible way to respond to the requested application” and the last error message in the idp-process.log was “DEBUG [org.opensaml.saml.common.profile.logic.DefaultLocalErrorPredicate:154] - No SAMLBindingContext or binding URI available, error must be handled locally”.
> 
>Please see the attached idp-processing.log fragment for more information. Any help is appreciated.

The SP is asking for a response to be returned, but there's no SLO endpoint in its metadata, so the IdP has no way to respond. That's my guess anyway.

-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net