Hi Antonio,
the certificate_privkey_export workflow is for downloading a key from
the datapool that was generated earlier by the WebUI based CSR workflow
so this is not really what you are looking for. The regular enrollment
workflow expects a properly formated CSR and there is nothing inside it
to generate a key pair or pass subject data alongside in the published
default workflows.
I guess the best way would be to use two workflows, one to generate the
private key and a matching CSR (needs to be build from scratch, likely
based on the WebUI workflow) and then send this CSR to the regular
enrollment workflow.
best regards
Oliver
Am 05.07.23 um 18:09 schrieb Antonio Gamboa:
Hi there.
I have been reading the documentation on workflows, but I can't figure
out how to define the process to generate the certificate and private
key on the server side (by using RPC API)
I think I need to use the workflow *def/certificate_privkey_expor*t,
but I am not sure how to pass the subject data in the RPC API POST
request.
Another question is about the certificate request approval, can it be
done from the RPC API?
I would really appreciate any information that can help me with this
configuration.
Thanks in advance.
I really appreciate this project.
_______________________________________________
OpenXPKI-users mailing list
OpenXPKI-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openxpki-users
--
Protect your environment - close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
OpenXPKI-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openxpki-users
