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 (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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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)
Do not place IBM confidential, company confidential, or personal information into any field.