Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:0.5
-
Epic Link:
-
Sprint:Fall 3: Oct 12 - Oct 23
Description
IGB installer build process uses a DigiCert-validated certificate to sign jars used by the Windows installers.
For this task, deploy the new certificate. Check that the build system works properly. Make sure that the installer can be run and IGB can start up as usual, with no scary warnings about IGB being "untrusted". Search Jira for past issues where this type of thing has occurred before.
Note that this ticket is private. The location of the key and its file name are confidential.
This needs to be done before releasing version 9.1.5 of IGB.
Attachments
Activity
I have renamed the new "pfx" file to "windows_keystore.pfx" and committed it to this branch:
This effectively replaces the existing (soon-to-be-expired) key with the new one made by Noor Zahara.
Noor Zahara - would you please ask a couple of the windows users tomorrow to try to install IGB using installer you created onto their systems?
If that works out OK, then I will merge the branch into the master branch. This will be enough to deploy the new key - no changes to the IGB code base will be needed.
Thank you!
Installed IGB on a windows machine using IGBF-2560 installer and it is working as expected.
Tested on windows machine. Installer ran without warnings. IGB opened as normal.
[~aloraine] - Karthik and Chirag have installed IGB on windows machine with no errors related to the certificate.
Merged PR from branch on iipc to master branch on upstream and updated master on iipc. The new key is now being used to sign jars in IGB main project pipeline.
To test, please confirm that the new master branch windows installers are working fine.
[~aloraine] - Has the certificate been uploaded ?