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 Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Nov 26, 2021

Fix the issue that's causing stuck of the JWT tokens from the z/OS Liberty server

A JSON Web Token(JWT) can get stuck. It manifests as /zosmf/services/authenticate endpoint issuing a JWT with success RC that is not valid for api calls, resulting in 401 rc. This is a persistent condition.

We are tracking two cases where it happens:

A) Using logout and passticket

1. login with Basic authentication and get JWT(basic)

2. call zOSMF with JWT(basic)
2. login same user with PassTicket

3. call zOSMF with JWT(passticket)
4. call zOSMF with JWT(basic)
5. logout JWT(basic)
6. call zOSMF with JWT(passticket)
7. login with Basic and get JWT(new basic)
8. call zOSMF with JWT(new basic) - this call fails with 401

B) Using fast logins only

If login is called repeatedly with high frequency in sequence, this is enough to cause that after some amount of calls, token that is issued with success response code is in fact invalid for api calls and results in a 401 response code.

Idea priority Urgent
  • Guest
    Nov 29, 2021

    This issue was raised via the following support case. We looked at it and found the workaround below. Unfortunately, the code fix requires a design work that is more than the support stream can handle. Posting the details for the evaluation purpose.

    TS005524772 (sev3 - CA INC)

    Symptom: Liberty finds the Subject from previously login by username/password authcache lookup. As a result, JWT token is reused.

    Root cause: Liberty removed incorrect authCache entry at the user logout, leaving the user's authCache entry. In the next login, the same Subject is used, and the same JWT token was reused.

    Workaround: Configure Liberty with following (Non default) so authcache is NOT looked up by the basic auth information.

    <authCache allowBasicAuthLookup="false" />

    Github issue: The following github issue has been opened. Ut spent time to investigate, but the code change is a little more involved than we thought.

    Closed as workaround was found. The change is involved... I was suggested in the scrum meeting to guide customer to open an Aha idea

    Dev comments:

    It was determined that there is an auth cache entries collision. The removal of the cached subject during the logout removes the subject that was created for the zOS passticket login, not the entries for its own login. Incorrect cache entry removal starts at this location.... (trace snippet follows)

    Trace snippets are on the internal site here: