Installing new Identity Certificates after changing hostname and IP address

Last Updated : Jul 06, 2021 |
Prolog information
Metadata
Keywords:
After updating the hostnames and IP addresses of the Experience Portal servers, new identity certificates need to be installed on the Experience Portal servers.
The Common Name and any Subject Alternate Name entries in the existing identity certificates for the Experience Portal servers contains the old hostname and IP address which is incorrect. The Common Name and Subject Alternate Name entries are used to validate a network entities identity during the setup of secure communications with that network entity.

Default Identity Certificates

If Experience Portal is using default identity certificates, you need to generate or upload a new EP Signing Certificate.
  • If using an EP Signing Certificate that was generated by Experience Portal, you need to generate a new EP Signing Certificate. For more information, see Generating a new EP Signing Certificate.
  • If using an EP Signing Certificate that was issued by an external CA, you need to upload a new EP Signing Certificate. For more information, see Uploading the EP Signing Certificate.

Custom Identity Certificates

If Experience Portal is using custom identity certificates, new identity certificates need to be installed for each Experience Portal server that has a change in their hostname and IP address.
The new custom identity certificates must have the Common Name and any Subject Alternate Name entries based on the new hostname and IP address of the Experience Portal server. The custom identity certificates are acquired from an external Certificate Authority.
For more information on installing custom identity certificates, see Uploading Identity Certificates.

Re-enabling Server Identity Validation

After updating the hostname, IP address, and identity certificates for the Experience Portal servers, you can re-enable Server Identity Validation.
For more information, see Enabling Server Identity Validation.