-
Notifications
You must be signed in to change notification settings - Fork 104
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
Work around Vault DB static creds TTL rollover bug #730
Merged
benashz
merged 8 commits into
main
from
VAULT-26529/vds-work-around-scheduled-static-creds-ttl-rollover
Jun 7, 2024
Merged
Work around Vault DB static creds TTL rollover bug #730
benashz
merged 8 commits into
main
from
VAULT-26529/vds-work-around-scheduled-static-creds-ttl-rollover
Jun 7, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benashz
force-pushed
the
VAULT-26529/vds-work-around-scheduled-static-creds-ttl-rollover
branch
from
May 8, 2024 14:48
498d725
to
0115e07
Compare
When syncing database static credentials role configured with scheduled rotation, the TTL is incorrectly rolled over within the same rotation period. Since, VSO relies on the TTL for its sync scheduling, an invalid TTL results in syncing stale credentials. This fix, attempts to detect the TTL rollover bug, and ensure that current rotated creds are properly synced.
benashz
force-pushed
the
VAULT-26529/vds-work-around-scheduled-static-creds-ttl-rollover
branch
from
May 8, 2024 14:52
0115e07
to
5d6bb40
Compare
…-creds-ttl-rollover
tvoran
approved these changes
May 10, 2024
benashz
force-pushed
the
VAULT-26529/vds-work-around-scheduled-static-creds-ttl-rollover
branch
from
May 22, 2024 18:25
fa31cba
to
145b47a
Compare
benashz
force-pushed
the
VAULT-26529/vds-work-around-scheduled-static-creds-ttl-rollover
branch
from
June 6, 2024 23:06
3a4ba37
to
3ae0af3
Compare
benashz
force-pushed
the
VAULT-26529/vds-work-around-scheduled-static-creds-ttl-rollover
branch
from
June 7, 2024 02:36
3ae0af3
to
cd70823
Compare
benashz
deleted the
VAULT-26529/vds-work-around-scheduled-static-creds-ttl-rollover
branch
June 7, 2024 13:28
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When syncing database static credentials role configured with scheduled rotation, the TTL is incorrectly rolled over within the same rotation period. Since, VSO relies on the TTL for its sync scheduling, an invalid TTL results in syncing stale credentials.
This fix, attempts to detect the TTL rollover bug, and ensure that current rotated creds are properly synced.