Missing/Additional fields in the RestAPI #466
Replies: 2 comments 4 replies
-
Assuming this is the endentity/add REST API. The swagger-ui of the latest release says:
So you can use key_recoverable. Status will be set to new/10 by default. There is another REST API call for setstatus. Set your installation to dev mode and hit the swagger-ui. https://localhost:8443/ejbca/swagger-ui Clear password is not supported, you should try to avoid clear passwords. It was really only (mostly) used for the 'bin/ejbca batch' CLI command. I think sendnotification has been up somewhere, let me check that. |
Beta Was this translation helpful? Give feedback.
-
Ah, since quite some time, if your end entity profile have "Notification - Use", and you add an email when adding the end entity through REST, then sendNotification is set automatically. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am trying to migrate our API from SOAP to REST. I have come across multiple fields that are not included in the RestAPI. I am not sure how can one include these fields in the request body of the RestAPI.
For instance, in the case of adding an end entity:
SOAP:
RestAPI documentation details the following fields:
How can one map the following fields:
Which one of the two if any is valid?
Beta Was this translation helpful? Give feedback.
All reactions