caa5661031
It's not obvious why this should be secret, and if it were considered secret, when and what anything would ever be allowed to access it. Likely the right way to tie secret values to particular entities/aliases/groups would be to use the upcoming templated ACL feature.
35 lines
872 B
Protocol Buffer
35 lines
872 B
Protocol Buffer
syntax = "proto3";
|
|
|
|
option go_package = "github.com/hashicorp/vault/logical";
|
|
|
|
package logical;
|
|
|
|
message Entity {
|
|
// ID is the unique identifier for the entity
|
|
string ID = 1;
|
|
|
|
// Name is the human-friendly unique identifier for the entity
|
|
string name = 2;
|
|
|
|
// Aliases contains thhe alias mappings for the given entity
|
|
repeated Alias aliases = 3;
|
|
|
|
// Metadata represents the custom data tied to this entity
|
|
map<string, string> metadata = 4;
|
|
}
|
|
|
|
message Alias {
|
|
// MountType is the backend mount's type to which this identity belongs
|
|
string mount_type = 1;
|
|
|
|
// MountAccessor is the identifier of the mount entry to which this
|
|
// identity belongs
|
|
string mount_accessor = 2;
|
|
|
|
// Name is the identifier of this identity in its authentication source
|
|
string name = 3;
|
|
|
|
// Metadata represents the custom data tied to this alias
|
|
map<string, string> metadata = 4;
|
|
}
|