Device Group Import Conflicts REST Service

Use Device Group Import Conflicts REST Service to list data conflicts, if any, when the device group data is imported from an export file into an IBM® Security Guardium® Key Lifecycle Manager instance. The conflicts must be resolved before the data can be imported. You can view the list of conflicts to analyze and resolve the problems.

Operation
POST
URL
https://<host>:<port>/SKLM/rest/v1/ckms/deviceGroupsImport/importConflicts
By default, Guardium Key Lifecycle Manager server listens to non-secure port 9080 (HTTP) and secure port 9443 (HTTPS) for communication. During IBM Security Guardium Key Lifecycle Manager installation, you can modify these default ports.
Note: The non-secure port 9080 is not applicable when IBM Security Guardium Key Lifecycle Manager is deployed in a containerized environment.

Request

Request Parameters
Parameter Description
host Specify the IP address or host name of the IBM Security Guardium Key Lifecycle Manager server.
port Specify the port number on which the IBM Security Guardium Key Lifecycle Manager server listens for requests.
Request Headers
Header name Value
Content-Type application/json
Accept application/json
Authorization SKLMAuth userAuthId=<authIdValue>
Accept-Language Any valid locale that is supported by IBM Security Guardium Key Lifecycle Manager. For example: en or de
Request body

JSON object with the following specification

Property name Description
importFilePath Specifies the location of the export file that contains device group data for importing into current instance of IBM Security Guardium Key Lifecycle Manager.
password Specifies the password that was used to encrypt the export file for importing and decrypting device group data into current instance of IBM Security Guardium Key Lifecycle Manager.

Response

Response Headers
Header name Value and description
Status Code
200 OK
The request was successful. The response body contains the requested representation.
400® Bad Request
The authentication information was not provided in the correct format.
401 Unauthorized
The authentication credentials were missing or incorrect.
404 Not Found Error
The processing of the request fails.
500 Internal Server Error
The processing of the request fails because of an unexpected condition on the server.
Content-Type application/json
Content-Language Locale for the response message.
Success response body

JSON object with the following specification

JSON property name Description
code Returns the value that is specified by the status property.
status Returns the status to indicate whether the data conflicts are listed with an appropriate message.
Error Response Body

JSON object with the following specification.

JSON property name Description
code Returns the application error code.
message Returns a message that describes the error.

Examples

Service request to list import conflicts during device group data import
POST https://localhost:<port>/SKLM/rest/v1/ckms/deviceGroupsImport/importConflicts
Content-Type: application/json
Accept: application/json
Authorization: SKLMAuth userAuthId=139aeh34567m
{"importFilePath": "C:\\BackupDir\\sklm_v3.0.0.0_20170728040703-1200_export.exp", 
"password": "passw0rd123"}
Success response
Status Code : 200 OK
 {"code":0,"keyIdConflicts":["KEY-ddd2652-1c6aa533-462a-41b9-8094-cfec83812e69","KEY-ddd2652-8eaf4710-4303-41d7-b3e3-bf8fd7c59fd7",
"KEY-ddd2652-b5d8f304-d2ad-4b47-94b1-220ff3b6a488"],
"keyAliasConflicts":["lto00ddd2652000000000","lto00ddd2652000000001","lto00ddd2652000000002"],
"keyGroupIdConflicts":["KEYGROUP-ddd2652-232cdeca-7a16-4622-acc4-e536e80df3a7"],"keyGroupNameConflicts":["LTO_Keygroup"]}
Error response
Status Code : 400 Bad Request
{"code":"CTGKM0631E","message":"CTGKM0631E  Missing required parameter \"  importFilePath  \" ."}