Trying to upload a public private key

I’ve been trying for two days to upload a certificate and private key to Apigee but keep getting the following message:

{
  "code": "messaging.config.beans.KeyParseFailure",
  "message": "Failed to parse the Key file : pearsonKey",
  "contexts": [],
  "cause": {
    "message": "Invalid passphrase or invalid rsa key, reason - expecting an rsa key",
    "contexts": []
  }
}

My key pair contains attributes specified at the top like so:

localKeyID: 37 35 34 38 36 36 35 30 30 37 33 39 34
friendlyName: apigee-dev
Key Attributes: <No Attributes>

Any help would be greatly appreciated!

Hi Dan,

I can’t tell from the error what the issue is, but the doc here on uploading a key, including creating the JAR file for the cert and private key, might help.

Stephen

Does OPDK 4.50 supports EC PRIVATE KEY ? As i am using EC private key and after creating jar while uploading getting below error

{
“code”: “messaging.config.beans.KeyParseFailure”,
“message”: “Failed to parse the Key file : xyz”,
“contexts”: ,
“cause”: {
“message”: “Invalid rsa key, reason - expecting an rsa key”,
“contexts”:
}
}

@dchiesa1 Any suggestions please ?

Does OPDK 4.50 supports EC PRIVATE KEY ? As i am using EC private key and after creating jar while uploading getting below error

{
“code”: “messaging.config.beans.KeyParseFailure”,
“message”: “Failed to parse the Key file : xyz”,
“contexts”: ,
“cause”: {
“message”: “Invalid rsa key, reason - expecting an rsa key”,
“contexts”:
}
}

Hmmm, I’m not clear. I think for 4.50, the answer is NO. RSA key only. For OPDK 4.52, YES.

There was a feature implemented to support ECDSA keys. The internal reference for that is b/67143653 . I believe that has been implemented, but not back-ported to OPDK 4.50. If you update to OPDK 4.52, you should have this feature.

1 Like

Thank you very much for quick response..! We are upgrading to 4.52.02 version