With the windows installer under control now is the time to loop back around and work out why.
The main purpose of this case it to be a publically visible (legible and persistent) engineering notebook.
Environment
None
Activity
Rod Widdowson
September 18, 2018 at 9:35 AM
One final comment before I resolve and close this case.
I managed to get a "standard installed" windows IdP to start forked by specifying idp.home using the short name and with forward slashes
-Didp.home=C:/Progra~2/Shibbo~1/IdP
Note that short names are not necessarily available in windows platforms since about Win7 time. DOS was old fashioned 25 years agoso you can see their point.
The setting of idp.home cannot be on the command line but has to be in the ini file. We knew this, precisely what threat this is working against I'm not sure.
Given the ease of stopping the windows install forking, the relative ease of debugging when it does (it whines about not finding the IdP home dir) , my ongoing concerns that the forking is done is a windows-secure manner, and the significant effort and turmoil needed to find the short name (and the possibility that they are not available) I am not going to do anything further towards doing this in the installer.
During https://shibboleth.atlassian.net/browse/IDP-1110#icft=IDP-1110 I discovered that various bad things happened if jetty forked on windows.
With the windows installer under control now is the time to loop back around and work out why.
The main purpose of this case it to be a publically visible (legible and persistent) engineering notebook.