Hi Andreas, Am 13.09.2018 um 09:30 schrieb [email protected]:
> still not working.
not working is not a qualified error message ;)
> The result is always:
>
> {"result":{"pid":7270,"id":0,"state":"SUCCESS","data":{"notafter":"2018-10-1
> 2T12:55:56","cert_identifier":"RE5XhSuJpvO9gpQCcC6srYvjHTk","status":"ISSUED
> ","notbefore":"2018-09-12T12:55:56"}}}
>
> (for SearchCertificate)
Exactly what I expect
> RequestCertificate also doesn't return the pem. Should this work out of the
> box?
The default workflow does NOT send the PEM, it just has the
cert_identifier in the workflow and the result should look similar to
the result above.
As said, to fetch the PEM you need to call
"Certificate.pem(context.cert_identifier)" which WILL BE implemented in
v2.2 (not released yet).
Oliver
--
Protect your environment - close windows and adopt a penguin!
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ OpenXPKI-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-users
