Sample Request/Response for Websphere Server
Sample Request
{
"certificateDetails": {
"isManualPush":true,
"certificateType": "JKS-.jks",
"keyStoreLocation": "/opt/automation/key.jks",
"keyStorePassword": "YXBwd==26",
"trustStoreLocation": "/opt/automation/trust.jks",
"trustStorePassword": "YXBwd==26"
"privateKeyInDevice": true,
"privateKeyLocation":"/opt/automation/keys",
"aliasName": "sampleKeystore"
},
"certificateId": "605dbd66ccb1c49e108e67e6",
"selectedProfiles": [
"WebsphereLinux:@8443:@localhost:@localhost:"
]
}
Sample Response
{
"response":[
{
"requestId":"58",
"connectorId":"WebsphereLinux:@8443:@localhost:@localhost:@51fb6d24534926ea1d89d32bfe59b25c26d84b5e"
}
],
"message":"1 connector(s) saved and push operation has been triggered.",
"appStatusCode":null,
"tags":{
},
"headers":null
}
Note: Above given sample request and response can be followed
for JKS certificate type (JKS.jks) for the Websphere server.
certificateId in the above request can be found using the search API
using commonName, serial No. or other search parameters.
resourceIdpresent in Search API response is equivalent to
certificateId here.
Sample Request
{
"certificateDetails": {
"isManualPush":true,
"certificateType": "PKCS12-.p12",
"keyStoreLocation": "/opt/automation/key.jks",
"keyStorePassword": "YXBwd==26",
"privateKeyInDevice": true,
"privateKeyLocation":"/opt/automation/keys",
"aliasName": "sampleKeystore"
},
"pushDetails": {
"preValidationScriptPath": "",
"postValidationScriptPath": "",
"pushAutomatically": false
},
"certificateId": "605dbd66ccb1c49e108e67e6",
"selectedProfiles": [
"WebsphereLinux:@8443:@localhost:@localhost:"
]
}
Sample Response
{
"response":[
{
"requestId":"59",
"connectorId":"WebsphereLinux:@8443:@localhost:@localhost:@51fb6d24534926ea1d89d32bfe59b25c26d84b5e"
}
],
"message":"1 connector(s) saved and push operation has been triggered.",
"appStatusCode":null,
"tags":{
},
"headers":null
}
Note: Above given sample request and response can be followed
for PKCS12 certificate type (PKCS12-.p12) for the Websphere server.
certificateId in the above request can be found using the search API
using commonName, serial No. or other search parameters.
resourceIdpresent in Search API response is equivalent to
certificateId here.