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 Submitted
Workspace WebSphere Liberty
Created by Guest
Created on Aug 29, 2024

Critcal need for passticket or IDT connection to Db2 for z/OS using persitent timer with zLiberty

Currently, the persistent timer in zLiberty only supports a password connection to Db2 for z/OS. This is very problematic for customers as it requires an outage for zLiberty whenever you need to change the persistent timer ID's password. We have also seen multiple situations now where a customer didn't change the password in time, and the user ID was revoked. An invalid password or revoked ID breaks our product's functionality as our daemons run using the persistent timer.

We need a non-password way of connecting to Db2 for z/OS for the persistent timer.

This should be fairly easy to implement as z/OS comes with the RACF Java libraries needed for requesting a passticket, which could then used as the password in a connection request to Db2 for z/OS. All we would need is a configuration option in the <persistentExecutor> section of the server.xml that tells the persistent timer to use a passticket for the connection (vs. a password).

Idea priority Urgent