SP v3 prerelease (windows)

[Alan Buxey]

hmm, okay - its just that we have a pool of servers and it would be
nice if we could keep the same single configuration repository for
deployment
but have a mix of v2 and v3 servers for the upgrade, I'm not talking
about turning shibboleth2.xml into shibboleth3.xml , I'm just meaning
that
shibboleth2.xml is left alone (for those doing whatever upgrades they
are doing....with a shibboleth3.xml.dist provided (with the correct
3.0 stuff
at the top etc) - those doing upgrade process such as myself could
simply copy current shibboleth2.xml to shibboleth3.xml , make required
changes
and be able to use same config directory on shib2 and shib3 SP service
deployments (then , when last v2 SP is switched off, delete
shibboleth2.xml

(I note the v3 IdP also uses shibboleth2.xml - same problems with RPM
etc I guess....perhaps same idea for IdP v4 with shibboleth4.xml ? )


alan