Metadata Generation

[Rod Widdowson]

> Right, removing the copy from idp-conf/src/main right now won't actually
> break anything, just not sure what we can do for the release. V2 only
> included the IdP's own metadata, which is now gone, so technically it
> should be empty, as long as that works. Not empty literally, probably with
> examples commented out.

I originally thought you meant the directory (which will still be used for
the idp's own directory and the backing store for HttpBacked metadata), but
of course you means the metadata-resolver.xml file - the directory is just a
directory.  

Getting the right default MetadataResolver.xml is a problem.  We need to
keep the tests running (which should just mean overloading the file in the
classpath), but we then have the issue of how well we work with no metadata.


At some time in the future I want to leave enough hooks in the windows
installer to allow federations to run a merge and add in their own key info
and metadata URLs, but sure as heck isn't for V3.0  

We did discuss (but didn't bottom out) adding in the Consortium members
metadata as examples, but I am unhappy about the transitive trust issues in
packaging someone else's keys.

Rod