This portal is to open public enhancement requests against IBM Z Software 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).
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.
See this idea on ideas.ibm.com
In z/OS Connect EE API requester, if requireSecure="true" and requireAuth="true" and are not overridden, then the "users" need to authenticate.
There are multiple authentication mechanisms that can be used, but the most common would probably be BasicAuth and client certificate.
For IMS and z/OS application, if BasicAuth is used, a BAQPASSWORD needs to be defined in clear text. Providing a clear text password is not really a good practice. If the password could be encoded in base64 or encrypted in AES (in a similar way than with the Liberty securityUtility), that would avoid setting a password in clear.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
IBM is proposing to address the issues behind this requirement by enabling the transparent assertion of the SAF identity from a CICS, IMS or other z/OS applications using the API requester capability, rather than taking an explicit credential (encrypted or otherwise) from environment variables, or CICS user exit. The strategic solution will be tracked by RFE 125402.
http://www.ibm.com/developerworks/rfe/execute?use_case=viewChangeRequest&CR_ID=125402