Importing an endpoint

You can move data across IBM Guardium Key Lifecycle Manager servers by importing endpoint data that is exported from another IBM Guardium Key Lifecycle Manager server.

Before you begin

  • Upload the export file to the system where
  • You must have the export file and ensure that you have the password that you used when the export file was created.
  • Version of the IBM Guardium Key Lifecycle Manager instance where the endpoint export data is being imported must be the same as the IBM Guardium Key Lifecycle Manager instance from which the endpoint data were exported.

About this task

To import an endpoint data, you can use graphical user interface or REST services. Your role must have a permission to import endpoints.

Sometimes the endpoint data that is imported might conflict with an existing data in the database. For example, a key in the imported endpoint might be a key with same alias name of an endpoint in the current instance of IBM Guardium Key Lifecycle Manager where the data is being imported. When conflicts occur, they must be resolved before the import process can continue.

For more information about endpoint export and import operations, see Overview of endpoint export and import.

Procedure

  • Using the graphical user interface
    1. Log in to the graphical user interface.
    2. On the home page, click the menu icon (Menu icon) at the upper left of the page.
    3. Click Data redundancy > Export and import.
    4. On the Export and import page, select the export file that you want to import and click the overflow menu icon (Options).
    5. From the overflow menu options, click Import.
    6. On the Import endpoint dialog, specify the encryption password that you used to create the export file.
    7. Click Import to start the import operation.
    8. If any conflicts arise during the import process, the Conflicts while importing dialog appears. Click Download conflict report to download the CSV file that contains the conflicts information. For more information, see Resolving the import conflicts.

      Else, when the import process is complete, a message box is displayed to indicate that the import operation is complete.

  • Using a REST interface
    1. Open the Swagger UI. For more information, see Using Swagger UI.
    2. Authenticate and authorize to access IBM Guardium Key Lifecycle Manager REST services. For more information about the authentication process, see Authentication process for REST services.
    3. Run the REST services as shown in the following examples.
      Endpoint
      POST https://localhost:port/GKLM/rest/v1/ckms/deviceGroupsImport
Content-Type: application/json
Accept: application/json
Authorization: SKLMAuth userAuthId=139aeh34567m
{"importFilePath": "C:\\Program Files\\IBM\\WebSphere\\Liberty\\products\\sklm\\data\\sklm_v5.0.0.0_20240328040703-1200_export.exp", 
"password": "passw0rd123"}
      Generic KMIP client endpoint
      POST https://localhost:<port>/GKLM/rest/v1/clientImport
Content-Type: application/json
Accept: application/json
Authorization: SKLMAuth userAuthId=a7e57bca-5591-468c-ad58-039bc6dc9670
{"importFilePath": "${SKLM_DATA}\\sklm_v5.0.0.0_20240310093243+0530_export.exp", 
"password": "my@Password123"}
      Client group endpoint
      POST https://localhost:<port>/GKLM/rest/v1/clientImport/importClientGroup
Content-Type: application/json
Accept: application/json
Authorization: SKLMAuth userAuthId=805afe85-6f73-4034-a02f-4d7f65dbf1f8
{"importFilePath": "${SKLM_DATA}\\sklm_v5.0.0.0_20240309172524+0530_export.exp", 
"password": "SKLM@admin123"}