Issues NonParticipant using Federation Metadata?

[Tom Scavo]

On Thu, Nov 2, 2017 at 4:33 PM, Peter Schober
<peter.schober at univie.ac.at> wrote:
>
> The way I consume metadata from sources I don't fully trust with
> secure/reliable production thereof is getting a snapshot of their
> metadata once and use only that (from a local file) in the IDP. Also
> commit it to a git repo (or whatever), and then periodically check for
> changes (e.g. `curl -sSo vendor.xml $URL`), e.g. with email
> notification if it changes (e.g. `git diff --exit-code vendor.xml`
> etc.) via cron.

Peter, that's a nice way to handle untrusted metadata. Have you
thought about filing an RFE that does most of that automatically? The
IdP already has curl and cron down pat.

> Since you then already have your own local copy why not also amend the
> local metadata with some XSLT script each time before diffing (and
> before checking in locally), say, if you wanted to move some
> configuration items into the metadata itself (e.g. NameIDFOrmat,
> RequestedAttribute, MDUI).

That could be done with entity attributes as well (which means the IdP
can do that already).

> Of course not even a local copy (even one kept up to date) won't save
> you from the ways an SP could mess up metadata production or key
> rollover.

That's true but flagging metadata as untrusted (as you have done
above) seems to be a reasonable middle ground.

Just my two cents.

Tom