Skip to main content
NetApp Knowledge Base

On GKLM the keys are tagged to old client certificate upon certificate rotation in ONTAP

  1. Last updated
  2. Save as PDF
Views:
82
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • External Key Management with IBM GKLM (Guardium Key Lifecycle Manager)

Issue

  • After renewing the client certificate in ONTAP and updating the configuration for IBM GKLM, it was observed that the new encryption keys generated after the certificate rotation are correctly tagged with the new client certificate on the GKLM server. However, existing keys created before the certificate rotation remain tagged with the old (expired) client certificate in GKLM.
  • Snippet from the GKLM server showing old and new certificate with encryption keys tagged to it

clipboard_b754e632-3f33-4eba-85ea-c548e51d9ca4.png

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.