Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Workspace WebSphere Liberty
Created by Guest
Created on Apr 15, 2024

Create a command to clear JWK Cache/Publickeys

We are experiencing an issue with zOS Connect/Liberty where the JSON Web Keys (JWKs) cached from a specific jwkEndpointUrl are not being refreshed unless there is a server recycle. This issue arises because our JSON Web Tokens (JWTs) do not use a new “kid” value when the keys are updated. As a result, Liberty continues to use the old, cached keys for validation, leading to authentication or authorization failures. To address this issue, we are requesting a command to manually clear the JWK cache in Liberty since we do not change our publickey/kid due to security reasons. This command would allow us to force Liberty to discard the old keys and fetch the new ones from the jwkEndpointUrl, ensuring that the system is always using the correct keys for validation. Some zOS Connect cache clearing commands do exist, just not for this JWK publickey. There is already a Liberty command to clear the authentication cache:, and this request is for a similar capability. The primary beneficiaries of this command would be system administrators managing Liberty, as it provides them with greater control and flexibility in managing system security and performance. This enhancement would significantly improve our ability to manage system security and performance, and streamline troubleshooting processes related to JWT validation.

Idea priority Medium