Skip to content
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

Make unbound keys expire with a different TTL in Vault #24

Open
gnarea opened this issue Jan 27, 2020 · 0 comments
Open

Make unbound keys expire with a different TTL in Vault #24

gnarea opened this issue Jan 27, 2020 · 0 comments
Labels
adapter-vault HashiCorp Vault enhancement New feature or request

Comments

@gnarea
Copy link
Member

gnarea commented Jan 27, 2020

(Bound key: A session key that can only be used with a specific recipient; unbound key: A node key or an initial session key)

Bound keys should expire after whatever TTL is set in Vault, but unbound keys should normally be kept around for much longer, so that default TTL should be overridden when unbound keys are created (which requires making a second API call unfortunately).

@gnarea gnarea added the enhancement New feature or request label Jan 27, 2020
@gnarea gnarea transferred this issue from relaycorp/awala-pong Mar 3, 2022
@gnarea gnarea transferred this issue from another repository Jun 13, 2022
@gnarea gnarea changed the title Make unbound keys expire with a different TTL Make unbound keys expire with a different TTL in Vault Jun 13, 2022
@gnarea gnarea added the adapter-vault HashiCorp Vault label Jun 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adapter-vault HashiCorp Vault enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant