Skip to main content

Update a server (v2)

PUT 

/tap/api/v2/servers/:serverId

deprecated

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 only in awsRoles: the request accepts AWS role objects, of which only id is read, as well as AWS role ids, and the response lists AWS role objects. 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. bundlePath in the response is the stored location of the certificate bundle, not a download link.

Request​

Responses​

The result of the update. When the change could not be saved, success is false and data is absent.