This is the public portal for all IBM Z Hardware and Operating System related offerings. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
N/A
That request would not match what my request is.
That request is to allow for password change, presumably allowing both the old password and new password to co-exist for a period of time.
My request is attempting to cover off broader cases, for example, a typo in JDBC datasource, or someone simply starting up a old JVM instance which may have -2 or -3 version of the password. This request is to avoid issues due to single password mishap which comes in repeatly due to 'machine persistent' authentication requests.
We have an existing high priority requirement which states that changing a password used by a process, such as a WebSphere application accessing DB2 through a JDBC Datasource protected by a J2C Authentication Alias, cannot be done without availability loss for the application. The requirement is for RACF to allow for a "password migration procedure". When changing the password of a RACF userid, the old password should remain valid for a certain period. In this period, both passwords can be used and you can use this period, for instance, to reflect the password change in different places, such as the J2C Alias. The period should be configurable and you should be able to display statistics about the usage of both new and old passwords, so that you can see if the old password is still being used.
If provided, would function such as this satisfy your requirement?
Creating a new RFE based on Community RFE #72509 in product z/OS.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - zSeries Software
Product - z/OS
Component - RACF
Operating system - IBM z/OS
Source - zBLC
For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - zBLC family
Product - zBLC
Component - zBLC Requirements
Operating system - IBM z/OS
Source - None