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

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 a notification 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.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Future consideration
Workspace DataPower Gateway
Created by Guest
Created on Jun 6, 2016

Allow LDAP queries from XSLT to take password maps

The LDAP query commands, dp:ldap-search(), ldap-authen() and ldap-simple-query() require the bind password to be in clear text.

Can the commands be enhanced to take a password map

Idea Priority High
Use Case
Customers don't want to store their bind passwords in clear text
RFE ID 89532
RFE Product IBM DataPower Gateways
  • Guest
    Nov 14, 2020

    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.

  • Guest
    Nov 19, 2019

    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.

  • Guest
    Nov 2, 2016

    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.


Add an extension function to return the literal password for a Password Map Alias

With the advent of recent firmware (7.2 series) use of the literal password is deprecated in the GUI by IBM, and for GUI configurable entries this appears comprehensive.However, with some integration work at USPS is has been required to execute dp...
about 6 years ago in DataPower Gateway 3 Not under consideration