Creating a custom SSL certificate for IFS Cloud using an internal Windows/Microsoft Certificate Authority fails IFS's own certificate verification with 'signature check failed,' even though the CSR, template, and export (with private key) all appear to have been done correctly.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

R&D's confirmed workaround for this: do the initial fresh installation using a self-signed certificate for whatever proxy combination you're using, and only afterward replace it with your internally-issued CA certificate by running update_http_certificates.sh to update the WebServer certificate. Trying to use the internal-CA certificate directly during the initial installation itself is what triggers the signature-verification failure; installing first with a self-signed cert and swapping it in afterward avoids the issue.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions