DynamicHTTPMetadataProvider

[Brent Putman]

On 9/20/16 9:24 AM, Tom Scavo wrote:
> Looking at the doc for IdP V3 DynamicHTTPMetadataProvider:
> https://wiki.shibboleth.net/confluence/x/o4AgAQ
>
> Can the base URL for the MDQ protocol start with "file://", 

No.  As its name suggests, that one is all about HTTP.   Not even sure
how you would expect plugging a file:// one into the MDQ option would
work, since AFAIK MDQ is defined entirely in terms of the HTTP protocol.

> that is,
> does the metadata provider support file-based metadata retrieval?

The HTTP one doesn't, and won't.  But there is a concrete plan for a
"local dynamic" one to resolve from a local filesystem.  It's probable
that it will be in 3.3.  You'll configure it with a base directory, and
then the metadata is resolved as the file content of that directory. 
Individual entity descriptor files will be named using a function-based
transform of the entityID, by default the SHA-1 hash.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160920/7a5aa5f9/attachment.html>