IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
When we create User IDs in RACF that will be used for Connect Direct transmissions, we have to create them with passwords so that the password can be used in the SPOE record. With a password is can make this User ID have the capability to signon. The password only needs to be known to RACF and the SPOE.
Should the User ID receive a password change in RACF, then every record for that User ID in SPOE has to be updated with the current password.
RACF has a attribute called PROTECTED which means it does not have a password and can not be used to Logon. Usage of PROTECTED IDs appears more secure since the User ID could not be used for any Logon purposes and no longer has a password.
Requesting that the product support the usage of RACF User IDs that are PROTECTED in SPOE.
|What is your industry?||Banking|
How will this idea be used?
Many organizations do not want to assign permanent passwords to service accounts, due to the exposure of the password becoming known, and being used without knowledge. So organizations are switching to changing service account passwords on a routine basis.
If the RACF Password is changed then the password stored in SPOE has to change as well. The password change has to be coordinated to occur at nearly the same time to ensure there are no disruptions with data transmissions using the User ID/Service Account.
Creating the User ID/Service Account as PROTECTED removes the need for keeping the password in sync between RACF and SPOE.
Do not place IBM confidential, company confidential, or personal information into any field.