Consider Splitting the Windows Installer into IdP and Jetty+Procrun

With the beta out, lets call this closed

Testing (as noted above) complete. We are ready for Beta, but I need to WTFM

In side discussions we need to add a warning dialog to the effect that if you are not using our jetty then you own the problem of locking down the installation and maintaining that.

We probably also need revert the default location back to PF86.

In PF86

• Make sure noone you don’t want to can read credentials or conf

Otherwise

• Make sure noone you don’t want to can read or write anywhere

In all cases

• Our jetty installer will lock things down appropriately (see documentation).

We might add a batch file to do this. If we added it to the “core” Module then the jetty installer could use it (any my wouldn’t that make life easier). https://shibboleth.atlassian.net/browse/IDP-2150

4->5 update fails because of potential previous ownership of files. Need to force ownership to (say) Administrators

I have just pushed the changes to mainline and deleted the test branch. Significant tested (as noted above) now needs to happen.