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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 Dec 22, 2020

Allow usage of z/OSMF JWT tokens by multiple sessions using the same user ID

We are using new APIs to obtain JWT tokens (/zosmf/services/authenticate) from our automated scripts that use other z/OSMF REST APIs with the obtained. After the script completes, it calls the DELETE method to invalidate the token that it obtained. When there are multiple scripts running at the same time or a person using a web UI with the same credentials, the DELETE method or logout will invalidate all the sessions and the scripts fail.

It seems that the JWT token that is returned for the exact values of user ID and password are all always the same so the logout (DELETE) done by the client, invalidates tokens that other clients have. It prevents reliable programmatic usage of z/OSMF REST API from programmatic API clients because the token obtained by one client can be invalidated by another one. It seems as unexpected behavior since using a different case (e.g. ?uSeRiD? or ?USERID ? instead of ?USERID?) or different PassTickets leads to different JWT tokens that are not invalidated by the DELETE method on other JWT tokens for the same user.

The requested behavior that is present in other software that generates JWT tokens is to generate different tokens for each login request (i.e. each session).

Since the tokens are used from independent sessions (different script, or web UI), we would expect that the POST /zosmf/services/authenticate will return different tokens for different sessions and the DELETE will delete just the token for one session. The expiration should be the configured duration from the moment of the request.

We agree that there can be a use case to invalidate all tokens of a user. The current behavior does not achieve that since tokens.

The expected behavior (different tokens for each POST request) is important for using REST API programmatically from multiple applications at the same time. Current behavior makes the usage of JWTs problematic because they can be invalidated at any moment by another application that is using them.

There is no good workaround for the problem. If the script does not use DELETE itself, there can be other scripts that call it.

Idea priority Medium
RFE ID 147555
RFE URL
RFE Product WebSphere Application Server