KesselInventoryService_CheckSelfBulk
Performs bulk permission checks where the subject is implicitly the caller (self) for multiple resource-relation combinations.
This API is more efficient than making individual CheckSelf calls when verifying permissions for multiple items. It answers questions like: “Which of these resources can the current caller perform action Y on?”
The response includes a result for each item in the request, maintaining the same order.
Request Body required
Section titled “Request Body required ”CheckSelfBulkRequest allows checking multiple permissions for the caller (self) in a single request. This is more efficient than making individual CheckSelf calls when verifying permissions for multiple resource-relation combinations.
object
CheckSelfBulkRequestItem represents a single permission check for the caller (self) in a bulk request. The subject is derived from the caller’s authenticated identity rather than being provided explicitly.
object
object
object
Defines how a request is handled by the service.
object
The service selects the fastest snapshot available. Must be set true if used.
All data used in the API call must be at least as fresh as found in the ConsistencyToken. More recent data might be used if available or faster.
object
Responses
Section titled “ Responses ”OK
CheckSelfBulkResponse contains the results of all self-access permission checks in the request.
object
CheckSelfBulkResponsePair associates a self-access request item with its corresponding result.
object
CheckSelfBulkRequestItem represents a single permission check for the caller (self) in a bulk request. The subject is derived from the caller’s authenticated identity rather than being provided explicitly.
object
object
object
CheckSelfBulkResponseItem represents the result of a single self-access permission check.
object
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
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.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
object
default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
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.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.