constellation/keyservice/keyserviceproto/keyservice.proto

syntax = "proto3";

package kms;

option go_package = "github.com/edgelesssys/constellation/v2/keyservice/keyserviceproto";

service API {
    rpc GetDataKey(GetDataKeyRequest) returns (GetDataKeyResponse);
}

message GetDataKeyRequest {
    string data_key_id = 1;
    uint32 length = 2;
}

message GetDataKeyResponse {
    bytes data_key = 1;
}
AB#1943 Extract KMS package (#56) * Extract kmsapi from coordinator * Add kmsapi cmd server 2022-05-10 06:35:17 -04:00			`syntax = "proto3";`

Add aTLS endpoint to KMS (#236) * Move file watcher and validator to internal * Add aTLS endpoint to KMS for Kubernetes external requests * Update Go version in Dockerfiles * Move most KMS packages to internal Signed-off-by: Daniel Weiße <dw@edgeless.systems> 2022-06-29 10:13:01 -04:00			`package kms;`
AB#1943 Extract KMS package (#56) * Extract kmsapi from coordinator * Add kmsapi cmd server 2022-05-10 06:35:17 -04:00
kms: rename kms to keyservice In the light of extending our eKMS support it will be helpful to have a tighter use of the word "KMS". KMS should refer to the actual component that manages keys. The keyservice, also called KMS in the constellation code, does not manage keys itself. It talks to a KMS backend, which in turn does the actual key management. 2023-01-11 04:08:57 -05:00			`option go_package = "github.com/edgelesssys/constellation/v2/keyservice/keyserviceproto";`
AB#1943 Extract KMS package (#56) * Extract kmsapi from coordinator * Add kmsapi cmd server 2022-05-10 06:35:17 -04:00
			`service API {`
			`rpc GetDataKey(GetDataKeyRequest) returns (GetDataKeyResponse);`
			`}`

			`message GetDataKeyRequest {`
			`string data_key_id = 1;`
			`uint32 length = 2;`
			`}`

			`message GetDataKeyResponse {`
			`bytes data_key = 1;`
			`}`