include SignatureValidation filter with FileBackedHTTPMetadataProvider

[Tom Scavo]

On Thu, Dec 21, 2017 at 9:13 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
>> I'm not clear why there are two HTTPMetadataProviders. If the only
>> difference between the two is the backing file, you only need one
>> MetadataProvider, right? Is there some historical basis for having
>> two? If you have any insight, please let me know.
>
> I alluded to that earlier. Other than code factoring I don't know why two types are needed for any normal deployment. I suppose there could be embedded scenarios where that code might be useful to somebody that couldn't back the file up.

Sure, but in any case, why are two HTTPMetadataProviders needed? Why
couldn't there be just one, with an optional backingFile attribute?

I'll create a jira issue along these lines tomorrow unless someone
suggests otherwise.

Tom