This portal is to open public enhancement requests for IBM Sterling products and services. 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
Use Refresh token rotation to make Jwt token more secure
Current Situation: An access token allows temporary access to restricted resources, PEM APIs, and so has a short validity period of 5 minutes (configurable through system properties). A refresh token has a longer validity as it allows users to log in and stay connected without providing their passwords for longer periods. Note that refresh token generation requires a user to provide their username and password. Shortening its lifespan will result in users having to reauthenticate themselves every few minutes (depending on the refresh token validity).
Suggested Situation: Make use of Refresh Token Rotation so every time the user authenticates, the app will generate new access and refresh tokens and return to the browser. The app should also persist the new refresh token to the database.
Whenever the browser requests then backend with the refresh token to get a new access token, the app generates a new refresh token and save it to a database. Next, the app will invalidate the refresh token that was just used.
This will avoid session hjjacking as also the tokens are showed in the URL with a GET request .
Do not place IBM confidential, company confidential, or personal information into any field.