Skip to Main Content
IBM Cloud - Structured Ideas

This portal is to open public enhancement requests against IBM Cloud and its 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.

IBM Cloud Support Center ( – Use this site for any IBM Cloud defect or support need.

Stack Overflow ( – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud". - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Jul 6, 2017

Ltpatoken2 cookie causing conflict in Login/UAA Bluemix component


we have detected with IBM experts a cookie conflict between BNPP applications and Bluemix Login UAA application (Ltpatoken2 cookie). 

It is not simple to change the cookie behavior on our side : the cookie is set at xxx.xxxxx level in order to share authentication between different hosts so we cannot "lower" the level from domain to host. Furthermore, we have pointed out one application, which does not mean that it is the only one that will use this cookie (we have somewhat 2000 WebSphere applications so an impact analysis is not practicable).

Does your UAA login component uses in any way this Ltpatoken2 cookie ? 

If yes, could you rename it (this is just a config parameter) ; this should not impact any client using Bluemix local as you hopefully don't share this cookie with other domains or hosts. 

If no, can you modify the Liberty config to ignore this cookie which should not disturb other client either, or if not possible, rename it anyway so that your Liberty component is not disturbed by this cookie presence. We will also provide directives to application developers on our side so that they rename this cookie if they use Liberty core runtime.

An incident ticket has also been posted (Ticket #5377-13483209)

Thank you in advance.

Idea priority High
  • Guest
    Oct 26, 2017

    Hello, Is this still an ongoing issue?