You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the Format is Base64 (PKCS #8), PKCS #12, or JKS, you can specify whether to return the private key
I expect to receive a certificate response with the certificate in JKS format, including the private key.
Actual behavior
An error is received:
Parameter set cannot be resolved using the specified named parameters. One or more parameters issued cannot be used together or an insufficient number of parameters were provided.
I think part of the issue that the $IncludePrivateKey property doesn't have the TppJks parameter set included here
However in a trace when testing, to provide the IncludePrivateKey property in the request body, you have to specify the field PasswordandKeyStorePassword if you want the exported certificate to be in the JKS format:
In the above screenshot, Request 27 included the chain, but not the IncludePrivateKey property:
In Request 36, you'll notice the body size increased from 3,270 to 6,230. The request for that included both the Password and IncludePrivateKey property:
* Mask CertficateData property in Write-VerboseWithSecret. Resolves#25
* Add IncludeChain support for JKS in Export-VenafiCertificate. Fixes#24
* Add IncludePrivateKey support for JKS in Export-VenafiCertificate. Fixes#26
* Update Export-VenafiCertificate example to correct function name
* Updates to Export-VenafiCertificate based on review feedback
Summary
The
Export-VenafiCertificate
function doesn't supportIncludePrivateKey
with theJKS
format.Environment
Windows
Linux
Steps to reproduce
On TPP (not VaaS), attempt to export a certificate with the following call:
Expected behavior
The docs state for
IncludePrivateKey
:I expect to receive a certificate response with the certificate in
JKS
format, including the private key.Actual behavior
An error is received:
I think part of the issue that the
$IncludePrivateKey
property doesn't have theTppJks
parameter set included hereAdding the parameter set is fine:
However in a trace when testing, to provide the
IncludePrivateKey
property in the request body, you have to specify the fieldPassword
andKeyStorePassword
if you want the exported certificate to be in theJKS
format:In the above screenshot, Request 27 included the chain, but not the
IncludePrivateKey
property:In Request 36, you'll notice the body size increased from 3,270 to 6,230. The request for that included both the
Password
andIncludePrivateKey
property:Screenshots
The text was updated successfully, but these errors were encountered: