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 Sep 14, 2021

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.

Idea priority Urgent
  • Guest
    Sep 15, 2021

    IBM product ELM has a RFE, "ELM session timeout interval should start counting up from user's last access", which cannot be realized without this RFE's functionality.

    http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=151469


  • Guest
    Sep 15, 2021

    Some IBM products based on Liberty have the LTPA SSO time out issue because Liberty does not have this functionality.