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 (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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Is a defect
Workspace WebSphere Liberty
Created by Guest
Created on Jun 1, 2026

New configuration to disable error BadPaddingException when server starts with different keystore_password

 Due to the changes in WAS Liberty 26.0.0.4 "LTPA keysPassword default value removal" and setting keystore_password, we now get error BadPaddingException on each new server startup, because the password in keystore_password differs from the default one. Previously, when default password was used, we had no such exception and therefore we could copy the file ltpa.keys on all servers  (as they should be identical to share SSO across multiple Liberty application instances).

It would help greatly when we could disable this error, which also generates FFDC file:

FFDC1015I: An FFDC Incident has been created: "javax.crypto.BadPaddingException: Given final block not properly padded com.ibm.ws.security.token.ltpa.LTPAKeyInfoManager 274"

Because we are using cluster environment, then each pod means new server instance and again this error.

When it's a normal behaviour described also here Enhanced JWT validation, Java 26 support, and more in 26.0.0.4- OpenLiberty.io "...then the keystore_password is used to reencrypt the LTPA keys that were previously encrypted with the default keysPassword when the server starts." then it would be better, if the error like this wouldn't be thrown and FFDC generated.

It confuses alerting based on FFDC files presence and amount of error logs.

Thanks a lot

Idea priority Low