Update a server (v1)
PUT/tap/api/v1/servers/:serverId
This endpoint has been deprecated and may be replaced or removed in future versions of the API.
Deprecated; use PUT /tap/api/v3/servers/{serverId}. Differs from v3 in awsRoles and bundlePath: the request accepts AWS role objects, of which only id is read, as well as AWS role ids; the response lists AWS role objects; and a non-empty bundlePath in the response is replaced with a presigned download link valid for 12 hours by default, or left as the stored location when the link cannot be generated. 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. An AWS role id the server does not already have must belong to an existing AWS role. 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/v3/servers/{serverId}/certificate/bundle builds a bundle without the server's certificate until the certificate is rebuilt. Requires the admin role.
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, awsRoles is not a list of AWS roles or AWS role ids, or awsRoles adds an AWS role id that does not exist.
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.