When attempting to add an account that utilizes SSH Keys for password rotation I get the following error:
"error": {
"code": 400, "message": "Bad Request: PAM-CMN-0467: A Password Authority problem prevented completing the request. Message: No response from Password Authority. Check log for details."
I added the correct deviceId and applicationId to the appropriate fields before hitting the "Try it out!" button.
I entered the json below into the POST section for devices:
note: the public and private key are base64 encoded as the documentation suggests.
{
"accountName":"p-capam",
"aliasNames":null,
"attributes":{
"keyOptions":null,
"verifyThroughOtherAccount":"false",
"discoveryAllowed":"f",
"publicKey":"ssh-rsa AAAAB3NzaC1ycLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUM== root@capam",
"protocol":"SSH2_PUBLIC_KEY_AUTH",
"passphrase":"Test$1234",
"privetKey":null,
"otherAccount":null,
"descriptor2":null,
"discoveryGlobal":"f",
"descriptor1":null,
"extensionType":"unixII",
"useOtherAccountToChangePassword":"false",
"passwordChangeMethod":"USE_SUDO"
},
"cacheBehavior":null,
"cacheDuration":null,
"description1":null,
"description2":null,
"password":"-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,7EA3AAELOREUMIPSUM
FhB6IgY43X8r84OEFmcrLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUMLOREUMIPSUM==
-----END RSA PRIVATE KEY-----",
"passwordViewPolicyId":null,
"privileged":"t",
"synchronize":"t",
"useAliasNameParameter":null
}
Is this a known issue? What log can I check for details? Any help or suggestions would be GREATLY appreciated.