Shibboleth Developers

[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?

Thanks in advance,
Tom