Shibboleth Developers

[Christopher A Bongaarts <>]

In the immortal words of Tom Scavo:
> AFAIK Shibboleth has always required metadata to be configured on a
> per-file basis.  It would be more convenient (and less error prone)
> for deployers if there were a configurable metadata directory  Then
> all you have to do is drop a metadata file into the directory and go.
> 
> So my question is why does Shibboleth require metadata *files* to be
> configured (as opposed to directories)?  Is the implementation choice
> merely historical in nature or is there some potential security
> vulnerability that I'm not seeing?

I'm guessing it's "nobody's asked for it yet"....

I think it would be a useful feature.   Would you like to write it up
in JIRA or should I? ;)

%%  Christopher A. Bongaarts  %%  

       %%
%%  Internet Services         %%  http://umn.edu/~cab  %%
%%  University of Minnesota   %%  +1 (612) 625-1809    %%