# Auto-rotation of certs and the cert auth method

**URL:** <https://discuss.hashicorp.com/t/auto-rotation-of-certs-and-the-cert-auth-method/52492>\
**Category:** Vault\
**Created:** [April 8, 2023, 10:20pm UTC](https://discuss.hashicorp.com/t/auto-rotation-of-certs-and-the-cert-auth-method/52492 "2023-04-08T22:20:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MWinther](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/mwinther/32/32386_2.png) [@MWinther](https://discuss.hashicorp.com/u/MWinther)\
**Post date:** [April 8, 2023, 10:20pm UTC](https://discuss.hashicorp.com/t/auto-rotation-of-certs-and-the-cert-auth-method/52492/1 "2023-04-08T22:20:18Z")

</div>

Is there a suggested workflow to keep certificates updated with the cert auth method and rotation using consul-template? I am getting ready to use consul-template for downloading a new certificate when needed, but it seems that once I do I will no longer be able to login or renew my token, and saving it to disk and letting the client push it back to vault seems a bit strange? Maybe that’s just me.