Oddness running from a daemon.

[Rod Widdowson]

To wrap this up, 

- My major problem was that I had idp.home specified with windows native
separators, not java/Unix native separators.  I'm wondering whether we need
to capture this bug in a FAQ area? I'm guessing its going to be a common one
- unless of course all windows users use the installer to install Jetty at
which stage they'll not see the problem.

- With some minor tinkering to my ldap-authn config I can now get logged in
and back successfully to the SP.

For the record, these are the properties changed in conf\idp.properties:

idp.entityID
idp.sealer.storePassword
idp.sealer.keyPassword
idp.scope

And these are the properties changed in jetty-base\start.d\idp.ini (for
Jetty)

jetty.host=0.0.0.0
jetty.https.port=443
jetty.backchannel.port=8443
jetty.backchannel.keystore.path=C:/Program Files
(x86)/Shibboleth/IdP/creds/idp-backchannel.p12
jetty.browser.keystore.path=C:/Program Files
(x86)/Shibboleth/IdP/creds/idp-userfacing.p12
jetty.backchannel.keystore.password
jetty.browser.keystore.password
jetty.backchannel.keystore.type=PKCS12
jetty.browser.keystore.type=PKCS12
jetty.war.path=C:/Program Files (x86)/Shibboleth/IdP/idp.war
jetty.jaas.path=C:/Program Files (x86)/Shibboleth/IdP/conf/authn/jaas.config

I'll make the changes to the MSI installer to ake sure that idp.home is
always set correctly (for jetty installs).  

Again, I'd like to apologise to Scott for sending on a wild goose chase with
this one.

Rod