Specified AssertionConsumerService Location as Relative Url

[Ian Young]

> On 29 Jun 2015, at 09:04, Rod Widdowson <rdw at steadingsoftware.com> wrote:
> 
>> Location="/SSOServiceProvider/SSO" 
> 
> Not that it helps you, but I'm pretty sure that that is Schema Invalid, so it could be argued that V2 had a bug.  But Scott will be authoratitive.

It's not schema-invalid, as the schema says xs:anyURI, but it is invalid per SAML Core section 1.3.2: all URI values are REQUIRED to be absolute. As Peter says, "relative to where?". The only place it could be relative to would be the metadata document itself, which makes no sense.

Use an absolute URI in the metadata.

    -- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5250 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20150629/6b7e8c18/attachment-0001.p7s>