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

Azure secrets engine, ability to specify static SPN secret expiry #178

Closed
jpetblk opened this issue Nov 30, 2022 · 2 comments · Fixed by #199
Closed

Azure secrets engine, ability to specify static SPN secret expiry #178

jpetblk opened this issue Nov 30, 2022 · 2 comments · Fixed by #199
Labels
enhancement New feature or request

Comments

@jpetblk
Copy link

jpetblk commented Nov 30, 2022

We require the flexibility to specify the expiration for secrets associated with static Service Principals in Azure. Vault hard-codes the expiration to 10 years. Our policy requires these secrets to be rotated every 6 months and for us to set expiration dates accordingly. The TTLs we will be assigning to Azure Secrets Roles in Vault will be well short of 6 months for the most part.
@heatherezell heatherezell added the enhancement New feature or request label Dec 6, 2022
@jhauray
Copy link

jhauray commented Feb 2, 2023

Hello,

We need the same improvement. Secrets expiration is limited to 6 month by our security team.

@austingebauer
Copy link
Contributor

Thanks, this seems like a reasonable request. I'm going to transfer it to https://github.com/hashicorp/vault-plugin-secrets-azure.

@austingebauer austingebauer transferred this issue from hashicorp/vault Jan 5, 2024
gsantos-hc added a commit to gsantos-hc/vault-plugin-secrets-azure that referenced this issue May 1, 2024
@gsantos-hc
feat: add explicit_max_ttl to azure secrets
df91eef 
Add `explicit_max_ttl` to Azure role attributes. If set, Application
Secrets in Azure AD will be created with a maximum lifetime equal to
`explicit_max_ttl` instead of the hard-coded 10-year default in effect
until now.

Fixes hashicorp#178
Fixes VAULT-12316
@gsantos-hc gsantos-hc mentioned this issue May 1, 2024
Merged
5 tasks
gsantos-hc added a commit to gsantos-hc/vault-plugin-secrets-azure that referenced this issue May 3, 2024
@gsantos-hc
feat: add explicit_max_ttl to azure secrets
0fb38e1 
Add `explicit_max_ttl` to Azure role attributes. If set, Application
Secrets in Azure AD will be created with a maximum lifetime equal to
`explicit_max_ttl` instead of the hard-coded 10-year default in effect
until now.

Fixes hashicorp#178
Fixes VAULT-12316
gsantos-hc added a commit to gsantos-hc/vault-plugin-secrets-azure that referenced this issue Jun 21, 2024
@gsantos-hc
feat: add explicit_max_ttl to azure secrets
3f7198c 
Add `explicit_max_ttl` to Azure role attributes. If set, Application
Secrets in Azure AD will be created with a maximum lifetime equal to
`explicit_max_ttl` instead of the hard-coded 10-year default in effect
until now.

Fixes hashicorp#178
Fixes VAULT-12316
gsantos-hc added a commit to gsantos-hc/vault-plugin-secrets-azure that referenced this issue Jun 25, 2024
@gsantos-hc
feat: add explicit_max_ttl to azure secrets
2f79d8d 
Add `explicit_max_ttl` to Azure role attributes. If set, Application
Secrets in Azure AD will be created with a maximum lifetime equal to
`explicit_max_ttl` instead of the hard-coded 10-year default in effect
until now.

Leases are renewable unless or until the remaining Azure-side lifetime
is shorter than the role's configured TTL. Marking a lease as
non-renewable signals to clients that they must obtain a new
lease/secret when the existing one is approaching the limit that was
originally set through `explicit_max_ttl`.

Fixes hashicorp#178
Fixes VAULT-12316
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: explicit max ttl for secrets gsantos-hc/vault-plugin-secrets-azure
4 participants
@austingebauer @jhauray @heatherezell @jpetblk