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.

Sign up for GitHub

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

Jump to bottom

Refactor StsRemoteClientConfiguration #4412

Closed
wolf4ood opened this issue Aug 13, 2024 · 0 comments · Fixed by #4413
Closed

Refactor StsRemoteClientConfiguration #4412

wolf4ood opened this issue Aug 13, 2024 · 0 comments · Fixed by #4413
Assignees
@wolf4ood
Labels
enhancement New feature or request

Comments

@wolf4ood
Copy link
Contributor

Feature Request

The StsRemoteClientConfiguration should hold the clientSecretAlias instead of directly the secret and the RemoteSecureTokenService should load the secret from the vault at every request.

Which Areas Would Be Affected?

remote sts

e.g., DPF, CI, build, transfer, etc.

Why Is the Feature Desired?

It's preferred to not store at boot time the secret, but instead resolve the secret lazy when needed.
@wolf4ood wolf4ood added the enhancement New feature or request label Aug 13, 2024
@wolf4ood wolf4ood self-assigned this Aug 13, 2024
@github-actions github-actions bot added the triage all new issues awaiting classification label Aug 13, 2024
@wolf4ood wolf4ood mentioned this issue Aug 13, 2024
Closed
@ndr-brt ndr-brt removed the triage all new issues awaiting classification label Aug 14, 2024
@wolf4ood wolf4ood mentioned this issue Aug 14, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wolf4ood wolf4ood

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
2 participants
@wolf4ood @ndr-brt