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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.