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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Dec 4, 2017

Add originator IP address/port to LTPA token

If I log in to a web application running in WebSphere Liberty Profile (WLP) from one machine, I can use the generated LTPA token on another machine without logging in a second time. It would be good if the LTPA token contained information about the client machine such as IP address and port to prevent the token being reused from a different machine.

Idea priority Medium
RFE ID 113771
RFE Product WebSphere Application Server
  • Guest
    Aug 23, 2021

    In this situation, the test case is willingly handing the token to another client machine, and in such a case, the token is working as designed. Although we could harden this path further, our backlog is quite full and this suggestion would not be prioritized highly enough to implement it in a reasonable time. Our standard position is that we won't accept requests that we don't believe we will implement within 2 years.