Integration


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).


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:

Search existing ideas

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 your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.


Add a new idea Subscribe
Status Not under consideration
Workspace DataPower Gateway
Created by Guest
Created on Feb 21, 2018

RELATED IDEAS

ldap-search Timeout Setting

The ldap-search XSLT function timeout value is in seconds and not milliseconds. We would like to be able to specify milliseconds for the timeout.

Statement example (existing):
dp:ldap-search(address, port, bindDN, bindPassword, targetDN, attributeName, filter, scope, sslProxyProfile, ldapLBGroup, ldapVersion, ldapReadTimeout)

Idea priority High
RFE ID 116725
RFE URL
RFE Product IBM DataPower Gateways
  • Guest
    Reply
    |     Sep 12, 2018

    I feel like this change request hasn't even been read by IBM. The requirement here is to have the call timeout in LESS than a second, or perhaps 1.5 or 2.5 seconds, and not in multiples of a second. The page linked to is the API details for LDAP search. The parameter clearly specifies a timeout has to be provided in SECONDS. What if I want to 'timeout' the LDAP search if it takes longer than half a second (500 milliseconds) or 250 milliseconds? Then clearly I can't use Datapower to meet my SLA, because the smallest timeout I can provide for the LDAP search step is 1 seconds (1000 milliseconds). How can this problem be explained any clearer?

  • Guest
    Reply
    |     May 16, 2018

    You can use the combination of LDAP Read Timeout and Idle Timeout to handle connectivity, see https://www.ibm.com/support/knowledgecenter/en/SS9H2Y_7.6.0/com.ibm.dp.doc/ldap-search_cryptographicfunction.html

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.