---
title: When will the old public keys be removed from my JWKS endpoint once I enable the Web Keys beta feature?
description: When you enable the Web Keys beta, old public keys remain in your JWKS endpoint for a maximum of 30 hours to prevent invalidating existing sessions.
---

[Skip to content](https://help.zitadel.com/when-will-the-old-public-keys-be-removed-from-my-jwks-endpoint-once-i-enable-the-web-keys-beta-feature#main-content)

[![zitadel-logo\_text-dark (1)](https://help.zitadel.com/hs-fs/hubfs/zitadel-logo_text-dark%20(1).png?width=210&height=60&name=zitadel-logo_text-dark%20(1).png)](https://help.zitadel.com/?hsLang=en)

Open main navigation

Close main navigation

- [Documentation](https://zitadel.com/docs)

[Documentation](https://zitadel.com/docs)

 How can we help you?

- There are no suggestions because the search field is empty.

1. [ZITADEL Knowledge Base](https://help.zitadel.com/?hsLang=en)
2. [Default Settings](https://help.zitadel.com/default-settings?hsLang=en)
3. [Web Keys](https://help.zitadel.com/default-settings?hsLang=en#web-keys)

June 27, 2025

# When will the old public keys be removed from my JWKS endpoint once I enable the Web Keys beta feature?

## What happens with the previously existing public key? For how long will it be present in the JWKS endpoint response?

When you enable the Web Keys beta feature in your instance, two web key pairs are created with one activated, as the docs state.

The old key created before the WebKeys API will keep showing in the JWKS endpoint `{your_domain}/oauth/v2/keys` for a max of 30 hours.   
We keep the old public keys until they expire, so that existing sessions are not instantly invalidated.

Source: [https://github.com/zitadel/zitadel/blob/main/cmd/defaults.yaml#L745](https://github.com/zitadel/zitadel/blob/main/cmd/defaults.yaml#L745)

- [Getting Started](https://help.zitadel.com/getting-started?hsLang=en)
- [User Management](https://help.zitadel.com/user-management?hsLang=en)
- [Authentication & Login](https://help.zitadel.com/authentication-login?hsLang=en)
- [Security & Compliance](https://help.zitadel.com/security-compliance?hsLang=en)
- [Troubleshooting](https://help.zitadel.com/troubleshooting?hsLang=en)
- [Account & Subscription](https://help.zitadel.com/account-subscription?hsLang=en#main-content)

    - [Support](https://help.zitadel.com/account-subscription?hsLang=en#support)
    - [Billing (Pro)](https://help.zitadel.com/account-subscription?hsLang=en#billing-pro)
    - [Billing (Enterprise)](https://help.zitadel.com/account-subscription?hsLang=en#billing-enterprise)
    - [Zitadel Cloud Account](https://help.zitadel.com/account-subscription?hsLang=en#zitadel-cloud-account)
    - [Service Description](https://help.zitadel.com/account-subscription?hsLang=en#service-description)
- [Default Settings](https://help.zitadel.com/default-settings?hsLang=en#main-content)

    - [Web Keys](https://help.zitadel.com/default-settings?hsLang=en#web-keys)
- [Self-Hosting](https://help.zitadel.com/self-hosting?hsLang=en)

[![zitadel-logo\_text-dark](https://help.zitadel.com/hs-fs/hubfs/zitadel-logo_text-dark.png?width=210&height=60&name=zitadel-logo_text-dark.png "zitadel-logo_text-dark")](http://zitadel.com)

1 Embarcadero Center, Suite 1200  
San Francisco, CA 94111

<https://github.com/zitadel/zitadel> <https://x.com/zitadel> <https://www.facebook.com/zitadel.social> <https://www.linkedin.com/company/zitadel/> <https://zitadel.com/chat> <https://www.youtube.com/@zitadel>

Copyright © 2025 All rights reserved.