no NameID in an unsolicited SAML2 Response

[Cantor, Scott]

On 8/15/13 5:43 PM, "Tom Scavo" <trscavo at gmail.com> wrote:
>
>Okay, so we investigated further and discovered the SP was mistakenly
>configured to go by two names. In fact, there are two entity
>descriptors in metadata with the same endpoint location.

That's normally the issue.

>I gave the IdP the other SP name (via the unsolicited protocol string)
>and that did the trick. Apparently the SP doesn't recognize itself as
>having the other name.

It doesn't act like an alias, it's a setting that is applied based on the
application "context" the URL is mapped to. The only way to have two names
apply at the same time for a given request is in the obscure case that you
override the SP's name based on the IdP's name.

-- Scott