Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/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
Why is it useful?

User can invalidate JWT that was issued for some other reason and in a different context. This could then lead to a broaken functionality, e.g. in the automation pipeline.

Who would benefit from this idea? Anyone who is using zOSMF with JWT support.
  • 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

    https://github.com/OpenLiberty/open-liberty/issues/18697

    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:

    https://ibm.box.com/s/p29gaawa5utstut2jhr0b1ul3y6aspvu