Hi Oliver,
>> The result is always:
>>
>> {"result":{"pid":7270,"id":0,"state":"SUCCESS","data":{"notafter":"201
>> 8-10-1
>> 2T12:55:56","cert_identifier":"RE5XhSuJpvO9gpQCcC6srYvjHTk","status":"
>> ISSUED ","notbefore":"2018-09-12T12:55:56"}}}
>>
>> (for SearchCertificate)
>Exactly what I expect
I expected also a PEM Cert :)
>> 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
I got it now by just copy and & pasted the pem part from the Certificate.pm
from github, modified the workflow ;)
I always get the PEM back now when using the request and search certificate
method from REST.
So I'm happy right now :)
Keep up the good work :)
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
