Shibboleth Developers

[Tom Scavo <>]

On 7/11/05, Chad La Joie 
<>
 wrote:
> Tom Scavo wrote:
> 
> I can rename it to ext.copy.conf which is close to what the IdP uses
> (copy-idp-conf) but still matches the rest of the extension naming
> conventions (purposely different than the main build to cut down on name
> conflicts/mistakes).

The name doesn't really matter, I was just mentioning that in passing.

> > If true, copy ${ext.name}/etc to ${idp.home}/etc and overwrite
> > anything that's there.  If false (default), copy ${ext.name}/etc to
> > ${idp.home}/etc but do not overwrite any existing files.  This
> > precludes the need to modify the property after the initial install.
> 
> No, I do not want to copy stuff but not overwrite.  I think this could
> lead to bad things.  For example, in version 1.0 of an extension you
> have foo.xml.  Then in version 1.1 you have foo.xml with new, and
> required stuff, as well as bar.xml.  If you just copy bar.xml over you
> might get all sorts of odd errors because you foo.xml wouldn't have the
> new stuff in it.

Well, again, I have to fall back on first principles.  I have a SAML2
metadata file that the site administrator will maintain on a regular
basis.  The installer should provide a starter metadata file (which
may change from version to version) but it should never overwrite the
file the sysadmin is maintaining.  The installation instructions could
go like this:

1) Copy the starter metadata file to a user home directory.
2) Modify the IdP config file to point to this user metadata file.
3) ...

As long as the user follows these directions, the metadata file is
protected from subsequent uninstalls and re-installs.  Is this the
correct approach?

Tom