This is an IBM Automation portal for Integration 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.
email@example.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Why just LDAP queries. Should be for all url open calls.
That way admins can create the password map alias and developers can use it to call the services they wish to build without knowing the actual password ever.
Besides just catering for LDAP search queries, can this not be expanded a bit more.
For example, if DataPower were to call an API, the only way to store the ClientSecret would be by hard-coding it in the XSL or store it in a Parameter.
Wouldn't it be great if we were able to store the ClientSecret in the password alias and just refer to the password alias object in our code?
This keeps it secure.
Please implement. While it is possible to build custom stylesheets to encrypt and decrypt passwords stored in files on the appliance, so that the configuration files don't have to contain clear text passwords, this is very painful to build.
Other usage of LDAP such as in RBM and AAA policies is able (or perhaps forced) to use password maps rather than clear text passwords.