DynamicHTTPMetadataProvider

[Tom Scavo]

On Tue, Sep 20, 2016 at 12:29 PM, Brent Putman <putmanb at georgetown.edu> wrote:
>
> On 9/20/16 12:03 PM, Tom Scavo wrote:
>> On Tue, Sep 20, 2016 at 11:56 AM, Brent Putman <putmanb at georgetown.edu> wrote:
>>> ... 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.
>> Sounds reasonable. Is there a JIRA issue open for this work?
>
> Yes, you opened it. :-)
>
> https://issues.shibboleth.net/jira/browse/IDP-972

Thanks Brent :-)

I'm glad to hear V3.3 is a likely target. Is this firm enough so that
you feel comfortable updating the JIRA ticket to that effect?

I think it's okay to default to filenames based on the SHA-1 hash but
I hear that the Shibboleth MDA will default to filenames based on the
percent-encoded entityID. Is there synergy in coordinating the
defaults across projects?

Tom