Prerequisites:-

• Get a new certificate from your CA.
• We expect the certificate in pfx/pkcs12 format. If pfx/pkcs12 format cannot be created, please provide a certificate with private key and the pfx file can be generated.

Steps :- 

Stop the Vault services and IIS on the Vault server.

·         Put the new certificate into IIS on the Vault Server.

·         Change the Bindings in IIS to point to the new certificate under port 443.

·         Create the .PFX file for the new certificate if not already created.

·         Add the .PFX file of the certificate to the Trusted Root Certification Authorities\\Local Computer and the Trusted People\\Local Computer on the Vault server.

·         Run the Vault Configuration Tool (via Apps > BIOVIA on a Server), and update the certificate information in the appropriate fields. This step will update all the relevant Vault configuration files where the certificate is used, such as, the Vault Client Service. Ensure that the information is populated and correct in all the other fields in this dialog box( for ex User name and password for Foundation Connection etc).

Click “Save” to validate and then, click “Apply”. The above dialog box will become grey, and then, it will re-appear.

·         The Vault services will start running automatically. IIS (WWW Publishing Service and IIS Admin Service) will start running automatically.

·         Click “Cancel” in the Vault Configuration Tool to close the dialog box.

·         In a load balanced environment, perform this step on the other Vault servers too. Copy the .parameters file, which was created when you clicked "Save", and use it on all other Vault servers. When you run the Vault Configuration Tool on the other Vault Servers, click the button, “Load”, to load the parameters file. Check all the information, and then, click “Apply”, in order to implement the changes.