# Regular rotation of Signing keys

**URL:** <https://community.auth0.com/t/regular-rotation-of-signing-keys/50156>\
**Category:** JWT.io\
**Created:** [September 21, 2020, 8:05pm UTC](https://community.auth0.com/t/regular-rotation-of-signing-keys/50156 "2020-09-21T20:05:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![msriitd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/msriitd/32/24371_2.png) [@msriitd](https://community.auth0.com/u/msriitd)\
**Post date:** [September 21, 2020, 8:05pm UTC](https://community.auth0.com/t/regular-rotation-of-signing-keys/50156/1 "2020-09-21T20:05:06Z")

</div>

Are the signing keys provided by Auth0 hosted on `https://your-domain.us.auth0.com` static or gets rotated regularly? Is there a mechanism to make signing keys rotate automatically after a regular interval of time? I know that we can rotate them through the dashboard or from the API, but I am more concerned about the current behaviour of keys with respect to the regular rotation.

---

<div class="post-metadata">

**Author:** ![art.rosnovsky](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/art.rosnovsky/32/17937_2.png) [@art.rosnovsky](https://community.auth0.com/u/art.rosnovsky)\
**Post date:** [September 22, 2020, 11:48pm UTC](https://community.auth0.com/t/regular-rotation-of-signing-keys/50156/3 "2020-09-22T23:48:49Z")

</div>

Hey @msriitd! Welcome to the community! 👋

We do not rotate signing keys regularly or otherwise. You can do this manually from the Dashboard, as you mentioned, or using Management API:

> **[Auth0 Management API v2](https://auth0.com/docs/api/management/v2#!/Keys/post_signing_keys)**

(some more info on [managing signing keys](https://auth0.com/docs/tokens/manage-signing-keys))

---

<div class="post-metadata">

**Author:** ![msriitd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/msriitd/32/24371_2.png) [@msriitd](https://community.auth0.com/u/msriitd)\
**Post date:** [September 24, 2020, 9:56am UTC](https://community.auth0.com/t/regular-rotation-of-signing-keys/50156/4 "2020-09-24T09:56:46Z")

</div>

Thanks @art.rosnovsky, One more thing, if there is no regular rotation of signing keys then why there is `max-age=15` directive in the `Cache_Control` header in the response from the `jwk_url`?  
I am trying to automate the process of refreshing keys by parsing the `max-age` directive and it gives a wrong interpretation in case of `Auth0`.  
Can someone tell me what does that mean?

---

<div class="post-metadata">

**Author:** ![msriitd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/msriitd/32/24371_2.png) [@msriitd](https://community.auth0.com/u/msriitd)\
**Post date:** [September 28, 2020, 6:30am UTC](https://community.auth0.com/t/regular-rotation-of-signing-keys/50156/5 "2020-09-28T06:30:53Z")

</div>

Any update on this? @art.rosnovsky @team

---

<div class="post-metadata">

**Author:** ![art.rosnovsky](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/art.rosnovsky/32/17937_2.png) [@art.rosnovsky](https://community.auth0.com/u/art.rosnovsky)\
**Post date:** [October 2, 2020, 12:52am UTC](https://community.auth0.com/t/regular-rotation-of-signing-keys/50156/6 "2020-10-02T00:52:56Z")

</div>

My apologies for the delay, got real busy out here.

My understanding is that this `max-age` value addresses key rotation. Since you could rotate keys at any moment, it’s important to set short cache max age to make sure apps have new keys as soon as they are rotated.

What exactly are you using max-age for in your automation scenario?

---

<div class="post-metadata">

**Author:** ![art.rosnovsky](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/art.rosnovsky/32/17937_2.png) [@art.rosnovsky](https://community.auth0.com/u/art.rosnovsky)\
**Post date:** [October 17, 2020, 12:52am UTC](https://community.auth0.com/t/regular-rotation-of-signing-keys/50156/7 "2020-10-17T00:52:59Z")

</div>

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
