IdP 3.21 Windows MSI installer and Jetty

Doan, Tommy tdoan at smu.edu
Tue Jan 12 11:10:16 EST 2016


Assuming you have a PKCS12 certificate/key pair, that's all I had done on our Server 2012 R2 IdPs with IdP 3.1.2, one of which so far has been upgraded to 3.2.1. 

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Michael A Grady
Sent: Monday, January 11, 2016 10:06 PM
To: Shib Users <users at shibboleth.net>
Subject: IdP 3.21 Windows MSI installer and Jetty

So I had Jetty installed with Shib 3.2.1 using the Windows MSI. Instead of using the self-signed user/browser facing cert generated as part of the install, I want to now use an existing server cert file. So I change the settings for:

  jetty.browser.keystore.path
  jetty.browser.keystore.password

in ../Shibboleth/IdP/jetty-base/start.d/idp.ini , but that doesn't seem to be taking effect, even after stopping and starting the Shibboleth 3 IdP Daemon service multiple times. Is there something else I need to do to get that change to take effect? This is on Windows 2012r2 if that makes any difference.

--
Michael A. Grady
IAM Architect, Unicon, Inc.



More information about the users mailing list