Custom Certificate not replaced on VAMI for vRB

Working with a customer today configuring their vRealize Business for Cloud instance I found that they had previously installed the appliance and replaced the Self Signed SSL certificate with their own Custom Certificate as per the instructions on the VVD 4.2 install guide   

On browsing to the appliance  https://vrb.domain.local the certificate appeared as valid. However when I came onsite to check settings and carry out the final setup I noticed that the certificate on the VAMI page https://vrb.domain.local:5480 was showing as not trusted and appeared to still be the self signed certificate.

Clearly during the original replacement something went wrong and did not update as expected.

The issue was because the VAMI references its server.pem file in the /opt/vmware/etc/lighttpd directory and this hadnt been updated.

FIX

Renaming the current file to server.old and adding the customer custom certificate as  server.pem file and restarting the VAMI:

# service vami-lighttp restart

After that the certificate shows as Valid.