-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document rest and rpc api #31
Comments
Was there any movement on this...? Or any documentation elsewhere that can be used...? |
@j-cimb-barker Unfortunately detailed wiki document for APIs are currently missing. Nowadays I am super busy with another project within the company. I plan to get back to contributing to OVPM at the beginning of the new year. Untill then you can do the following to reach to reference docs for REST API. First you need to launch ovpmd as explained here and then you can access to the docs for each service by visiting the following url
gRPC API is similiar with the REST API. Proto files for the gRPC services can be examined here. |
Thanks for getting back to me. I have had some success by following the code and have been able to authenticate and use the Rest api. :) |
How can I submit the authentication token or username/password to the user/list endpoint once I authenticate ? I mean what are the params I need to submit in my post request ? |
You should include an Authorization HTTP header in your request:
|
How can I send a curl request for rest APIs. I mean what are the params I need to submit in my get and post request? |
Hi, Now I am able to get REST API response using curl command through token as below, curl -H "Accept: application/json" -H "Authorization: Bearer " MY_SERVER:8080/api/v1/auth/status In my case, I want to do all the things with ca-certificates. |
@vvek82 Unfortunately OVPM does not export internal PKI parameters to users at this point. |
Please add the doc links to the homepage :) |
Write a documentation for the ovpm REST and gRPC APIs. Put it up on the Wiki.
The text was updated successfully, but these errors were encountered: