Planning a WAF SSL certificate replacement: listener versus upstream certificates
The guide explains that replacing certificate files on an application server does not necessarily change the certificate visitors see, since a public HTTPS listener and an upstream application can present separate TLS identities. It contrasts the two locations, noting that the SafeLine documentation covers traffic routing but does not document certificate file paths, a replacement procedure, or a reload command. A comparison table sets out the verification target, ownership questions, and common mistakes for each certificate location. Before making changes, the author recommends recording the hostname, current expiration, certificate identity, and responsible component, and validating the new certificate's coverage, chain, and private key. The guide frames these as general operational distinctions rather than a verified SafeLine refresh procedure.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in