Remove an administrator from a computer's inventory
DELETE/computers/:computerId/admins
Removes an account from the inventory.
The account is identified in the request body (not the query string) by sid, or by id (user, group, or computer object id); sid wins when both are sent. A DELETE with no body, or with the id only in the query string, is 422 Missing required parameters. On Linux computers the account's sudoers entries are removed as well. There is no protection for the built-in administrator: removing the default admin account succeeds with 200.
Returns 409 Administrator not in inventory when the account is not in the inventory.
Required role: superadmin or admin.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
Administrator removed.
Linux only: the sudoers service rejected the update. Missing parameters are 422.
No token, or the token is invalid or expired. The body is {message}: No auth token provided when no token is sent, otherwise the token check's message (jwt expired, jwt malformed, invalid signature, invalid token, jwt signature is required). Send Authorization: Bearer <token> exactly: the server drops the first seven characters of the header and reads the rest as the token, so a different scheme or an extra space fails. If Authorization is absent, the server reads a token field in the body, then a token query parameter, then x-access-token. Routes that validate query fields reject ?token= with 400 InvalidQuery.
The token's role is not allowed for this operation, or the token's scopes exclude the route
(Scope not allowed by token).
No record has the :id in the path (the id is malformed or unknown). The body is the bare text Invalid <Type> ID (for example Invalid Computer ID, Invalid User ID) with Content-Type text/html; charset=utf-8, not JSON. Some routes return an empty body.
The request conflicts with the current state of the resource.
The request could not be processed, for example an id that is not a valid object id.