When exporting a JSON configuration from Unified Access Gateway (UAG) with multiple certificates configured, all Internet interface certificates are included in the exported JSON file (along with the certificates identifiers, default values, and certificate chains). This JSON file can be imported into a new UAG instance by providing the appropriate private keys during import.
Modify configured certificates
-
If there are any previously configured TLS certificates from the imported JSON, the certificates are listed on the TLS Server Certificate Settings section. To view the certificate chain information for a specific TLS certificate, click View.
-
The private key is not part of the exported JSON file. You can select the private key in PEM format or upload the whole keystore in PFX format for each of the certificates listed.
-
If any of the existing certificates from the imported JSON has already expired, you can upload a replacement certificate by selecting the Certificate Chain.
-
If any of the existing certificates from the imported JSON has already expired, you can upload a replacement certificate by selecting the Certificate Chain. You can also modify the default certificate by selecting the Mark as Default toggle against any of the certificates.
-
If none of the certificates are marked as "Default" during JSON import, whichever certificate already present as default in the new UAG will continue to be the default certificate.
Delete certificate(s) from JSON
If there are any previously configured certificates which are not going to be used for the new deployment, you can clean up the list using the Delete option. The deleted certificate entry is removed from the JSON file.
Was this page helpful?