Auto “renew” seems to actually create new certificates. Is there a way to get it to do a “real” renew (same private key) so that the thumbprint does not change?
We use octopus to do deployments - we use the same wildcard cert for all dev sites. This allows us to keep track of a single thumbprint within octopus and it binds to the cert with that configured thumbprint. However, we just had our first autorenew, and while it was added to the certificate store, it also has a different thumbprint so it is not being bound in iis (i’m currently using the option to ONLY add the cert to the certificate store and letting octopus do the rest).