IBM Cloud - Structured Ideas

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you

  1. Post an idea

  2. Vote ideas that matter most to you

  3. 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 notifications 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.

NOTE: All IBM employees must enter Ideas through this Ideas Portal.

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.

  • Guest
  • Jul 6 2017
  • Closed

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.