Thanks Oliver .. It worked

On 21/06/22 20:53, Oliver Welter wrote:

Hi,

a) use a client certificate and configure it properly in <realm>/rpc/enroll.yaml

b) rework the workflow to skip authentication (make sure to protect the interface by other means)

best regards

Oliver

On 17.06.22 13:11, Biswajit Banerjee via OpenXPKI-users wrote:

Hi Experts

We are able to generate Certificates via RPC api without any approval process . Now when we call the Revocation RPC Api by cert identifier , the process keeps waiting for approval , unless you login via roap and approves it .

Example Output

/curl     --data "method=RevokeCertificate"     --data "cert_identifier=oGIp1cwUdHdUCoc-5OiTSWQC5ZI"     --data "reason_code=unspecified" https://172.20.115.30/rpc/enroll -k | jq//
//
//{//
//  "result": {//
//    "state": "//*PENDING*//",//
//    "pid": 25629,//
//    "proc_state": "manual",//
//    "id": 452095,//
//    "data": {}//
//  }//
//}/

Need guidance for getting the revocation process automated bypassing the approval process .

Please help

TIA

Biswajit



_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
--
Protect your environment -  close windows and adopt a penguin!


_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users

Reply via email to