PopulateBindingAndEndpointContexts: Unable to resolve outbound message endpoint

[Cantor, Scott]

> 1)      Is V3.2.1 more strict about this AssertionConsumerService than 2.3.x?  Is
> the '&gid=1' suffix what is actually causing this problem?

Well, it doesn't match, so if they don't match, it's invalid. I don't know of any conscious change that would have allowed it to work before, but if it did work, that was a bug.

> 2)      If so, is there a way to make it less strict so we can accept this
> inconsistency for this SP until we work it out with them?

Not without changing code.

> 3)      Am I correct that the parameter skipEndpointValidationWhenSigned
> would not help in this situation?  I do see a message that "protocol message
> signature succeeded" earlier in the request.

It would certainly solve the problem if the request was signed, and I would be more likely to assume that your older IdP was using it if it worked.

-- Scott