Auto generating CSR is not available until Yokohama patch 7 <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Renewing TLS Certificates with AI Agents for Discovery The Certificate Inventory and Management application has been enhanced with a new feature that leverages AI Agents for Discovery to streamline the renewal of TLS certificates. Overview of the Renewal Process To renew a TLS certificate, two essential components must be generated: Private Key: A new, unique private key.Certificate Signing Request (CSR): A request sent to a certificate authority to obtain a digital certificate. As part of this process, the private key is generated on the MID Server and, for enhanced security, is stored in an external vault. Version-Specific Information Please note the following version requirements for the external vault integration: Yokohama: The integration required to store the private key in an external vault is not available until Patch 7.Zurich: This integration is available as a standard feature from the Zurich release onwards.Once the support is added, this KB will be updated with Yokohama patch details. Troubleshooting Known Errors When using the Yokohama version (prior to Patch 7), you may encounter issues related to MID Server configuration during the certificate renewal process. Error Message: If the MID server is not configured correctly, the following error message may be added to the work notes of the Renewal task: "Error occurred while writing private key to vault. Please try renewing the certificate manually." Common Causes: This error typically occurs due to one of the following reasons: Incorrect Vault Credentials: The credentials used to access the external vault are invalid.Improper Credential Configuration: The vault credentials have not been configured correctly on the instance.Vault Unavailability: The external vault is not running or is otherwise inaccessible from the MID server. If you encounter this error, please verify your vault and credential configuration or renew the certificate manually.