Skip to Main Content
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.


Status Future consideration
Workspace DataPower Gateway
Created by Guest
Created on Oct 18, 2023

Manage LDAP connections as it was done in V5

Hello,

as indicated in TS014138520 there is a problem in APICONNECT v10 when connecting to LDAP.

APIC v10 is not managing the connections correctly, and there is a port exhaustion, even when there are only 55 concurrent clients calling LDAP as shown in the ticket in a test scenario.


Two things should be explored:

1) Why are the ports not being freed correctly? This seems like a bug in your connection management.

2) In v5 a pooling connection was used for the LDAP authorization. Why is this functionality not used in v10? Can this functionality be implemented in v10 for Authentication and Authorization as well?


The proposed workaround in the case was to implement a multiprotocol gateway that managed the connections using the pooling that was used in V5.


Thank you.



Idea priority Urgent
2 MERGED

LDAP Connection Pools in default domain on DataPower

Merged
While no where near as busy as application domains, there are LDAP calls regularly from the default domain on a DataPower appliance. Particularly in the case of monitoring and maintenance tools that can cause dozens of LDAP calls per minute. Multi...
4 months ago in DataPower Gateway 0 Future consideration