Enabling public access to IFS Cloud shows the connection as insecure, with the certificate's CN not matching what's expected, even though internal/private-network access works fine.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Before suspecting the ingress controller's TLS certificate itself, check for a NAT rule on the firewall sitting in front of the public entry point — a NAT misconfiguration can forward public traffic to the wrong application server entirely (which is what actually presents the mismatched certificate), rather than the certificate or ingress configuration being the real problem.

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