-
Notifications
You must be signed in to change notification settings - Fork 485
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the key_metadata_file and use_msi (azure_key_vault only) settings #5207
Remove the key_metadata_file and use_msi (azure_key_vault only) settings #5207
Conversation
Signed-off-by: Agustín Martínez Fayó <amartinezfayo@gmail.com>
If you need more control over the identifier that's used for the server, the | ||
`key_identifier_value` setting can be used instead. This allows to specify a | ||
static identifier for the server instance, and is appropriate in situations | ||
where a key identifier file can't be persisted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you need more control over the identifier that's used for the server, the | |
`key_identifier_value` setting can be used instead. This allows to specify a | |
static identifier for the server instance, and is appropriate in situations | |
where a key identifier file can't be persisted. | |
If you need more control over the identifier that's used for the server, the | |
`key_identifier_value` setting can be used to specify a | |
static identifier for the server instance. This setting is appropriate in situations | |
where a key identifier file can't be persisted. |
|
||
Aliases managed by the plugin have the following form: `alias/SPIRE_SERVER/{TRUST_DOMAIN}/{SERVER_ID}/{KEY_ID}`. The `{SERVER_ID}` is an auto-generated ID unique to the server and is persisted in the _Key Metadata File_ (see the `key_metadata_file` configurable). This ID allows multiple servers in the same trust domain (e.g. servers in HA deployments) to manage keys with identical `{KEY_ID}`'s without collision. The `{KEY_ID}` in the alias name is encoded to use a [character set accepted by KMS](https://docs.aws.amazon.com/kms/latest/APIReference/API_CreateAlias.html#API_CreateAlias_RequestSyntax). | ||
The plugin assigns [aliases](https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html) to the Customer Master Keys that manages. The aliases are used to identify and name keys that are managed by the plugin. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The plugin assigns [aliases](https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html) to the Customer Master Keys that manages. The aliases are used to identify and name keys that are managed by the plugin. | |
The plugin assigns [aliases](https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html) to the Customer Master Keys that it manages. The aliases are used to identify and name keys that are managed by the plugin. |
If you need more control over the identifier that's used for the server, the | ||
`key_identifier_value` setting can be used instead. This allows to specify a | ||
static identifier for the server instance, and is appropriate in situations | ||
where a key identifier file can't be persisted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See other suggestion.
Consequently, if the file is lost, the plugin will not be able to identify keys | ||
that it has previously managed and will recreate new keys on demand. | ||
|
||
If you need more control over the identifier that's used for the server, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See other suggestion.
Signed-off-by: Agustín Martínez Fayó <amartinezfayo@gmail.com>
key_metadata_file
from theaws_kms
,azure_key_vault
andgcp_kms
plugins.key_identifier_file
andkey_identifier_value
settings are used.use_msi
setting from theazure_key_vault
plugin. A separate PR removing that setting from theazure_msi
plugin will be opened.