Shibboleth Developers

["Scott Cantor" <>]

> In the SAML 1.1 spec, the target parameter is alternately referred to
> as "TARGET" and "Target".  In Shibboleth, the parameter name is
> "target".  Is this inconsistency cause for concern or do
> implementations routinely work around case sensitivity of parameters?

There is no parameter in SAML that corresponds to the one in Shibboleth
called "target" because that's a request parameter and there is no request
in SAML. The one that is defined in SAML is called "TARGET" and Shibboleth
matches this.

There's a non-normative bit in the artifact profile that mentions something
called "TARGET" and "Target" in the same step, but it isn't a required part
of the spec and is internal to the IdP anyway, since it doesn't carry enough
information to drive a SAML response.

I would not personally write any code that tries to accommodate case in this
area.

-- Scott