No Peer Endpoint - At a loss

Etan Weintraub eweintra at
Thu Nov 1 11:20:43 EDT 2012

I'll look into the log shrinking, what about the error decoding when I switch them to HTTP-POST though...any ideas on that?

-Etan E. Weintraub
Sr. Systems Engineer
Directory Architecture
IT at Johns Hopkins
Johns Hopkins at Mt. Washington
5801 Smith Ave.
Suite 3110B
Baltimore, MD 21209
Phone: 410-735-7945
E-mail: eweintra at

-----Original Message-----
From: users-bounces at [mailto:users-bounces at] On Behalf Of Cantor, Scott
Sent: Thursday, November 01, 2012 11:19 AM
To: Shib Users
Subject: Re: No Peer Endpoint - At a loss

On 11/1/12 11:16 AM, "Etan Weintraub" <eweintra at> wrote:

>OK, so I made some changes and found some more info. New metadata looks
>like this:

Right, but their AuthnRequest explicitly says Redirect, so you just get a
failure. The log says this:

>11:10:51.737 - WARN
>[org.opensaml.saml2.binding.AuthnResponseEndpointSelector:202] - Relying
>party 'NetPartner' requested the response to be returned to endpoint with
>ACS URL ''  and
>binding 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect' however no
>endpoint, with that URL and using a supported binding,  can be found in
>the relying party's metadata

BTW, you might look into shrinking your log's stack traces with some
logging.xml magic, it helps a lot. I think one of the examples I posted in
the wiki shows how.

-- Scott

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

More information about the users mailing list