Get desktop application:
View/edit binary Protocol Buffers messages
The Mpa service definition
Store a request that we'd like to try running in the future. Requests are stored in-memory and older requests may be cleared automatically. This call is idempotent - requests from the same user with the same contents will return the same id. The user for the request and any justification is implicitly passed in via inspecting the peer of the RPC or via gRPC metadata.
The GRPC method name, as '/Package.Service/Method'
The request protocol buffer.
All approvers of the request. Storing is idempotent, so approvers may be non-empty if we're storing a previously approved command.
Approve a previously stored request. A request can have multiple approvals and can be approved by anybody but the original user that stored the request. The user for the request is implicitly passed in via inspecting the peer of the RPC or via gRPC metadata.
Approve takes an action instead of an ID to improve auditability and allow richer authorization logic.
(message has no fields)
Block until at least one approval has been granted. This is used as an optimization to avoid needing to poll for MPA approval.
(message has no fields)
List available requests.
(message has no fields)
Get a request and all approvals associated with it.
All approvers of the request.
Clear a stored request. This is typically unnecessary due to how requests are stored in memory and forgotten after a process restart.
(message has no fields)
Used in:
, , , ,The user that created the request.
User-supplied information on why the request is being made.
The GRPC method name, as '/Package.Service/Method'
The request protocol buffer.
Used in:
Used in:
, ,The principal identifier (e.g. a username or service role)
Auxiliary groups associated with this principal.