Per-Entity Metadata Working Group

[Christopher Hubing <>]

On Thu, 13 Oct 2016, Ian Young wrote:

> > On 13 Oct 2016, at 17:51, Christopher Hubing 
> > <>
> >  wrote:
> >
> > > > https://mdqtest.testbed.tier.internet2.edu/entities/urn:mace:incommon:uiowa.edu
> > > > https://mdqtest.testbed.tier.internet2.edu/entities/urn:mace:incommon:psu.edu
> > > > https://mdqtest.testbed.tier.internet2.edu/entities/urn:mace:incommon:osu.edu
> > > > https://mdqtest.testbed.tier.internet2.edu/entities/https://uwdcc.org/shibboleth
>
> Those '/' characters in the entityID part of the path in the last example 
> need to be encoded as %2f to be compliant with the spec. Otherwise they form 
> additional path components, which is not what you want.
>
> Client MUST use that encoding, so you MUST respond to it appropriately.

Thanks for pointing that out, all fixed up.

> > > Does your MDQ server support the SHA-1 hash version as well?
> >
> > It doesn't, but that wouldn't require much of a change to support. I'm 
> > looking through https://tools.ietf.org/html/draft-young-md-query-05 and am 
> > not seeing the format of the request to get the SHA-1 hash. Do you have a 
> > pointer?
>
> It's in the layered SAML profile spec:
>
> https://tools.ietf.org/html/draft-young-md-query-saml-05

Great. Thanks, Ian. I'll peruse the document this evening.

-c

> Enjoy,
>
>    -- Ian