Deploy keys and certificates to a module

Use this resource to deploy key manager certificates to a specific module keystore.

Request

To deploy a key or certificate, send a PUT request to the endpoint defined below.

URL: /keys

Method: PUT

Authorization: required (user with role System Administrator)

PUT /ibis/rest/keys HTTP/1.1
Accept: multipart/form-data
Host: localhost:8080

The following table lists the parameters for this request.

Name Description Required Allowed values

Name	Description	Required	Allowed values
`keystoreFile`	Upload the keystore file containing the keys or certificates.	yes	Any attachment
`moduleName`	Enter the name of the module associated with the keystore.	yes	Any string
`owner`	Enter the name of the module owner.	yes	Any string
`alias`	Enter the alias of the keystore entry.	yes	Any string
`privateKeyPassword`	Enter the password for the private key.	yes	Any string
`propertyName`	Enter the name of the keystore property corresponding to the module.	yes	Any string

keystoreFile

Upload the keystore file containing the keys or certificates.

yes

Any attachment

moduleName

Enter the name of the module associated with the keystore.

yes

Any string

owner

Enter the name of the module owner.

yes

Any string

alias

Enter the alias of the keystore entry.

yes

Any string

privateKeyPassword

Enter the password for the private key.

yes

Any string

propertyName

Enter the name of the keystore property corresponding to the module.

yes

Any string

Different connectors use different property names. Refer to the following examples:

The response returns a JSON object confirming the deployment status.

HTTP/1.1 200 OK
Content-Type: application/json

{
  "responsedata": "Created/updated successfully."
}

This request might return one of the following error codes:

Authorization Failed (401): Authorization with the given username and password failed. Please revisit both values and provide valid credentials.

{
    "statusCode": 401,
    "message": "Unauthorized access",
    "path": "/rest/<endpoint>",
    "timestamp": "2025-06-07T14:21:11.781"
}

Resource Not Found (404): The 404 (Not Found) status code indicates that the requested endpoint or resource is unavailable or does not exist on the server.
Server Error (500): Execution on the INUBIT server failed. Have a look into the response message, otherwise access to the INUBIT log is required to retrieve further information.

{
  "statusCode": 500,
  "message": "Internal Server Error",
  "path": "/rest/<endpoint>",
  "timestamp": "2025-08-06T12:55:31.862"
}

Service Unavailable (503): In maintenance mode the INUBIT server endpoint will not respond to incoming requests but return this error response. Once the maintenance mode is switched off the endpoint will respond normally.

{
  "statusCode": 503,
  "message": "Service Unavailable",
  "path": "/rest/<endpoint>",
  "timestamp": "2025-08-06T12:58:06.688"
}