How do we modify on-premises data gateway to support a custom connector for LDAP stores?

[t-elijaho]

Hi folk, I am working on a custom connector to connect to on-premises LDAP stores through the on-premises data gateway.

I need some clarification on if and how the gateway created needs to be modified to support a custom connector. The documentation says, it supports the existing connectors. See below. 

In Azure Logic Apps, the on-premises data gateway supports the on-premises connectors  for these data sources:

• BizTalk Server 2016
• File System
• IBM DB2
• IBM Informix
• IBM MQ
• MySQL
• Oracle Database
• PostgreSQL
• SAP
• SharePoint Server
• SQL Server
• Teradata

You can also create custom connectors  that connect to data sources over HTTP or HTTPS by using REST or SOAP. 

[SameerCh]

Those connectors are built-into the system.

Our extensibility model for on-premise system (like that on the cloud) is that we can talk to any REST API endpoint. So, you will need to construct a REST proxy to your system (in this case LDAP) first. Then, you can build a custom connector to it.

[t-elijaho]

Agreed. The part that is missing in understanding for me is the LDAP directories we are trying to connect to do not publicly expose their endpoint. So, we are currently looking towards the on-premises data gateway that acts like a middleman translator between the REST API and the LDAP protecting the data being sent. But currently, this data gateway doesn't support LDAP. How could we go about adding that capability? What would you advise?

[SameerCh]

We dont have the extensibility model to plug-in directly onto the gateway. The LDAP module (for lack of words) would have to be a separate installation. It would provide a REST API on one side and speak LDAP on the other. You would then hook up that LDAP module as an on-premise custom connector through its REST API.