Generating a self-signed certificate no longer produces a copy of the certificate file on the Management server the way it did in older environments, even though the generation step itself reports success.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

This is an intentional architecture change from around 23R1 onward — the self-signed certificate is now stored only as a Kubernetes secret inside the cluster (commonly named something like ifs-ingress.crt) rather than also being copied out to a file on the Management server; if you need the certificate content itself, retrieve it from the Kubernetes secret directly rather than looking for a file on the Management server the way older versions provided.

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