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 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
make authCache distributed within a Collective or a predefined set of servers
After migrating from WAS ND Classic with use of TAI and Custom Subject/Custom Cache key to Liberty the use of Liberty collectives has shown that, even with SSO login with LTPA configured, a new login is forced when accessing a server not beeing the server that created the Subject. And that effectively breaks our SSO in the existing applications.
A PMR is created for this and holds more information: https://www.ibm.com/support/servicerequest/readPMR.action?pmrNum=34493&branch=001&retainCountryCode=806
So this is a showstopper in our move from WAS Classic to Liberty. When TAI still is supported, included custom cache keys, we feel that Liberty should support the distribution of the authCache.
Maybe in the same way as httpSessions is distributed with the sessionCache-1.0
Do not place IBM confidential, company confidential, or personal information into any field.