Skip to content

Commit 547306e

Browse files
author
Donna-Marie Smith
committed
removed link that should not be present
1 parent dc6f2d7 commit 547306e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/docs/2024.9/getting-started/on-premise/install-innovation-only/advanced/rollover-certificates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ A new, valid X.509 certificate needs to be obtained to update the certificates.
2727
The certificate can be obtained from a Certificate Authority, such as [Let’s Encrypt](<https://letsencrypt.org/>), and must meet the following requirements:
2828

2929
* Subject field must be in one of the following formats depending on whether a multi-domain or wildcard certificate is used:
30-
* Multi-domain certificate - If using the [gobetween][] load balancer this should be specified as the FQDN of the load balancer server (e.g. `CN=load-balancer.domain.com`). If using a different load balancer this must be specified as the FQDN of one of the application servers (e.g. `CN=application-server.domain.com`)
30+
* Multi-domain certificate - If using the gobetween load balancer this should be specified as the FQDN of the load balancer server (e.g. `CN=load-balancer.domain.com`). If using a different load balancer this must be specified as the FQDN of one of the application servers (e.g. `CN=application-server.domain.com`)
3131
* Wildcard certificate - wildcard format, pertaining to the domain of the Application Servers (e.g. `CN=*.domain.com`).
3232
* Subject alternative names must include any additional host names that should be able to be used to access the API Gateway Service. Additionally if using a multi-domain certificate:
3333
* The FQDN, NetBIOS Name and IP address of all application servers must be added.

0 commit comments

Comments
 (0)