Update a server (v2)
PUT/tap/api/v2/servers/:serverId
Updates a server. Only fullName, email, active, custodianName, domains, and awsRoles are read; a field that is omitted or null is left unchanged, and every other field, including csr, is ignored. When email domain validation is on, the resulting email is checked even when email is not sent. Changing fullName or domains does not issue a new certificate. Certificate files are stored under a name derived from fullName, so after fullName changes, download links point to a bundle that does not exist and POST /tap/api/v2/servers/{serverId}/certificate/bundle builds a bundle without the server's certificate until the certificate is rebuilt. Requires the admin role. bundlePath in the response is the stored location of the certificate bundle, not a download link.
Request
Responses
- 200
- 400
- 403
- 404
- 422
- 500
The result of the update. When the change could not be saved, success is false and data is absent.
The identifier is not a number.
The caller does not have the admin role.
No server exists with the given identifier, or the identifier belongs to a user.
Email domain validation is on and the resulting email domain is not allowed.
The server could not be updated, including when the request body is not a JSON object or a field has the wrong type.