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,
Post an idea
Upvote ideas that matter most to you
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 email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
LTPA token timeout should respond to user activity
This is a requirement for ISO 27001 certification. This type of functionality is required by many security teams, and it is really hard to justify, explain, and get security deviations. It would be useful because users would not be harassed by frequent and unexpected sudden log in requests, whereby they lose data.
At present, the LTPA SSO time out is decided at user log in according to the configured time. It does not matter that a user is performing actions and is actively entering information into a Web browser or clicking buttons etc., the time out will occur at the specified time. It would be so much better if the time out were extended through such activity and the log out not occur until after the activity subsided.
One of the main causes of issue is that session time outs are restricted to the primary login window. Spawning multiple sessions does not "reset" the timeout clock. Users tend to work in multiple browser windows, login in to one and at times spawning multiple duplicate tabs. If the users main focus of changes is in one of these spawned/secondary windows, if no updates are done in the primary window, session timeout will occur. This causes any spawned windows to also terminate, losing any changes made by the user.
Do not place IBM confidential, company confidential, or personal information into any field.