Revoke takes one subject's own grants off many servers, the servers by id or by tag. Like Grant it is one transaction and one access change.
https://app.nokku.sh/nokku.v1.TargetAccountService/RevokeTry it
Header Parameters
Define the version of the Connect protocol
Define the timeout, in ms
Authorization
BearerAuth (bearer)
A service account token. Include it in the Authorization header: `Authorization: Bearer <token>`
CookieAuth (cookie: __Host-nokku_session)
The session cookie the web app uses. Browsers send it after sign-in. Only on `localhost` it is named `nokku_session`.
Request Body
Requiredapplication/json
revokeWhose grants go where. A server counts when its id is named or it has one of the tags. Only the subject's own grants go, what a team gives its members stays.
subjectid?kind?targetIds?tags?Responses
200Success
200Success
application/json
plan?What it did.
grants?Grants that go, one per account and server.
servers?Servers they are on.
accounts?The accounts, the one on the most servers first.
otherTags?Servers among them with more than one tag. The access goes for those tags too.
otherTagNames?Some of their names.
defaultError
defaultError
application/json
Error type returned by Connect: https://connectrpc.com/docs/go/errors/#http-representation
code?The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
message?A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
details?A list of messages that carry the error details. There is no limit on the number of messages.