Wildcard SSL Cert. Jetty Windows IDP

[Rod Widdowson]

> 1.       Are we able to use an existing Wildcard SSL certificate on a
Jetty webserver? We have a cert in .pfx format.

PFX is PKCS12.  You might want to just check this by poking at it with
OpenSSL.  (openssl pkcs12 file.pfx)

> 2.       How do we import the PFX certificate? Should we be using Keytool
for this?
Absolutely not.  Just make sure that jetty.browser.keystore.type is set to
PKCS12

> We then edited the IDP.ini file to point the “jetty.browser.keystore.path”
to the imported cert. 
> We also updated the “jetty.browser.keystore.password”. Upon doing this,
the Shibboleth 3 IDP 
> Daemon service will not stay started.

Sounds like you did exactly the right thing.  Time to check the logs.

Your best bet will be idp\jetty-base\logs\<mumble>STDOUT.LOG  should tell
you something: 
For instance: 

java.lang.IllegalStateException: no valid keystore or
Java.IO.IOException: keystore password was incorrect

Failing that check idp\logs\ipd-process.log and (although it's highly
unlikely) procrun\log\*

> Are there step by step directions to get through this process out there? 
> We are replacing an old Shibboleth server that has reached end of life. 

Nothing beyond 

https://wiki.shibboleth.net/confluence/x/MwAUAQ#WindowsInstallation-JettyCon
figuration

Which you seem to have found and be following.

Rod