LDAP
The LDAP connector lets you configure a generic LDAP server.
Supported versions
This connector supports LDAP versions 2 and 3.
Before you begin
Before using the LDAP connector, do the following tasks:
- In your Google Cloud project:
- Ensure that network connectivity is set up. For information about network patterns, seeNetwork connectivity.
- Grant theroles/connectors.admin IAM role to the user configuring the connector.
- Grant the following IAM roles to the service account that you want to use for the connector:
roles/secretmanager.viewerroles/secretmanager.secretAccessor
A service account is a special type of Google account intended to represent a non-human user that needs to authenticate and be authorized to access data in Google APIs. If you don't have a service account, you must create a service account. The connector and the service account must belong to the same project. For more information, seeCreating a service account.
- Enable the following services:
secretmanager.googleapis.com(Secret Manager API)connectors.googleapis.com(Connectors API)
To understand how to enable services, seeEnabling services.
If these services or permissions have not been enabled for your project previously, you are prompted to enable them when configuring the connector.
Configure the connector
A connection is specific to a data source. Itmeans that if you have many data sources, you must create a separate connectionfor each data source. To create a connection, do the following:
- In theCloud console, go to theIntegration Connectors > Connections page and then select or create a Google Cloud project.
- Click+ CREATE NEW to open theCreate Connection page.
- In theLocation section, choose the location for the connection.
- Region: Select a location from the drop-down list.
For the list of all the supported regions, seeLocations.
- ClickNEXT.
- Region: Select a location from the drop-down list.
- In theConnection Details section, complete the following:
- Connector: SelectLDAP from the drop down list of available Connectors.
- Connector version: Select the Connector version from the drop down list of available versions.
- In theConnection Name field, enter a name for the Connection instance.
Connection names must meet the following criteria:
- Connection names can use letters, numbers, or hyphens.
- Letters must be lower-case.
- Connection names must begin with a letter and end with a letter or number.
- Connection names cannot exceed 49 characters.
- Optionally, enter aDescription for the connection instance.
- Optionally, enableCloud logging, and then select a log level. By default, the log level is set to
Error. - Service Account: Select a service account that has therequired roles.
- Optionally, configure theConnection node settings:
- Minimum number of nodes: Enter the minimum number of connection nodes.
- Maximum number of nodes: Enter the maximum number of connection nodes.
A node is a unit (or replica) of a connection that processes transactions. More nodes are required to process more transactions for a connection and conversely, fewer nodes are required to process fewer transactions. To understand how the nodes affect your connector pricing, see Pricing for connection nodes. If you don't enter any values, by default the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.
Note: You can customize the connection node values only if you are a Pay-as-you-go customer. - Base DN: The base portion of the distinguished name, used for limiting results to specific subtrees.
- Auth Mechanism: The authentication mechanism to be used when connecting to the LDAP server.
- Follow Referrals: Whether or not to follow LDAP referrals returned by the LDAP server.
- Friendly GUID: Whether to return GUID attribute values in a human readable format.
- Friendly SID: Whether to return SID attribute values in a human readable format.
- LDAP Version: The LDAP version used to connect to and communicate with the server.
- Scope: Whether to limit the scope of the search to the whole subtree (BaseDN and all of its descendants), a single level (BaseDN and its direct descendants), or the base object (BaseDN only).
- Optionally, click+ ADD LABEL to add a label to the Connection in the form of a key/value pair.
- ClickNEXT.
- In theDestinations section, enter details of the remote host (backend system) you want to connect to.
- Destination Type: Select aDestination Type.
- To specify the destination hostname or IP address, selectHost address and enter the address in theHost 1 field.
- To establish a private connection, selectHost Address and add the endpoint attachment created for the SAP Gateway using the HTTPS protocol. Note:To understand how to create an endpoint attachment, seePSC service attachment andendpoint attachment. After you have created the endpoint attachment, it will be visible in theEndpoint Attachment list.
If you want to establish a public connection to your backend systems with additional security, you can considerconfiguring static outbound IP addresses for your connections, and then configure your firewall rules to allowlist only the specific static IP addresses.
To enter additional destinations, click+ADD DESTINATION.
- Destination Type: Select aDestination Type.
- ClickNEXT.
- Select anAuthentication type and enter the relevant details.
The following authentication types are supported by the LDAP connection:
- Username and password
- ClickNEXT.
To understand how to configure these authentication types, seeConfigure authentication.
Configure authentication
The LDAP connector supports the basic authentication type. If your destination or LDAP instance is hosted on a VM or is in a private network,create an endpoint attachment. For information about how to install and configure LDAP, seeLDAP installation.
- Username and password
- Username: Username for connector
- Password: Secret Manager Secret containing the password associated with the connector.
Basic authentication connection type
The following table lists the sample configuration values for the Basic authentication connection type.| Field name | Details |
|---|---|
| Region | us-central1 |
| Connector | LDAP |
| Connector version | 1 |
| Connection Name | google-ldap-basicauth-conn |
| Service Account | SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com |
| Base DN | CN=Users,DC=NAME,DC=com |
| Auth Mechanism | SIMPLE |
| LDAP Version | 3 |
| Scope | WHOLESUBTREE |
| Verbosity Level | 5 |
| Minimum number of nodes | 2 |
| Maximum number of nodes | 50 |
| Username | USER_NAME |
| Password | PASSWORD |
| Secret Version | 1 |
Entities, operations, and actions
All the Integration Connectors provide a layer of abstraction for the objects ofthe connected application. You can access an application's objects only through this abstraction. The abstraction is exposed to you as entities, operations, and actions.
Note: You can view the entities, operations, and actions of a connector in theConnectors task.- Entity:An entity can be thought of as an object, or a collection of properties, in theconnected application or service. The definition of an entity differs from a connector to a connector. For example, in a database connector, tables are the entities, in a file server connector, folders are the entities, and in a messaging system connector, queues are the entities.
However, it is possible that a connector doesn't support or have any entities, in which case the
Entitieslist will be empty. - Operation:An operation is the activity that you can perform on an entity. You can performany of the following operations on an entity:
Selecting an entity from the available list, generates a list ofoperations available for the entity. For a detailed description of the operations, see the Connectors task'sentity operations. However, if a connector doesn't support any of the entity operations, such unsupported operations aren't listed in the
Operationslist. - Action:An action is a first class function that is made available to the integrationthrough the connector interface. An action lets you make changes to an entity or entities, and vary from connector to connector. Normally, an action will have some input parameters, and an output parameter. However, it is possible that a connector doesn't support any action, in which case the
Actionslist will be empty.
Actions
This section lists all the actions supported by the LDAP connector.
Note: The results of all the actions will be available as a JSON response in theConnectors task'sconnectorOutputPayload response parameter after you run your integration.MoveToDN action
This action moves objects from one DN (distinguished name) to another DN.
Input parameters of the MoveToDN action
| Parameter Name | Data Type | Required | Description |
|---|---|---|---|
| DN | String | Yes | The current DN of the object to be moved on the LDAP server. For example,CN=Google Cloud,OU=Bangalore,OU=India,OU=Domain_Users,DC=test-ldap,DC=com. |
| NewParentDN | String | Yes | The new parent DN of the object. For example,OU=Mysore,OU=India,OU=Domain_Users,DC=test-ldap,DC=com. |
Output parameters of the DownloadFile action
This action returns the status 200 (OK) with a response body indicating the results.
To understand how to configure theMoveToDN action, seeAction examples.
GetAttributes action
This action gets all the attribute names and values of a DN.
Input parameters of the GetAttributes action
| Parameter Name | Data Type | Required | Description |
|---|---|---|---|
| DN | String | Yes | Distinguished name of the desired LDAP object. If unspecified, the BaseDN from the connection string will be used. |
Output parameters of the GetAttributes action
This action returns the status 200 (OK) with a response body indicating the results.
To understand how to configure theGetAttributes action, seeAction examples.
AddMembersToGroup action
This action adds users to a group.
Input parameters of the GetAttributes action
| Parameter Name | Data Type | Required | Description |
|---|---|---|---|
| GroupId | String | Yes | ID of the group to which you want to add the users. |
| UserDNs | String | Yes | The UserDNs aggregate or a temporary table that contains the DN of the users to be added to the Group. The value should be the DN of the user record. |
Output parameters of the AddMembersToGroup action
This action returns the status 200 (OK) with a response body indicating the results.
To understand how to configure theAddMembersToGroup action, seeAction examples.
Action examples
This section describes how to perform some of the actions in this connector.
Example - Move an object from one DN to another DN
- In the
Configure connector taskdialog, clickActions. - Select the
MoveToDNaction, and then clickDone. - In theTask Input section of theConnectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{"DN":"CN=Google Cloud,OU=Bangalore,OU=India,OU=Domain_Users,DC=test-ldap,DC=com","NewParentDN":"OU=Mysore,OU=India,OU=Domain_Users,DC=test-ldap,DC=com"}
This example moves an object from one DN to another DN. If the action is successful, your connector task'sconnectorOutputPayload response parameter will have a value similar to the following:
[{"Success":null,"result":"[ok]","modified":"true","rss:title":"The movement was successful.","resultcode":"0"}]
Example - Get attributes of a DN
- In the
Configure connector taskdialog, clickActions. - Select the
GetAttributesaction, and then clickDone. - In theTask Input section of theConnectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{"DN":"CN=Bangalore user,OU=Bangalore,OU=India,OU=Domain_Users,DC=test-ldap,DC=com"}
This example gets the attribute of the specified DN. If the action is successful, your connector task'sconnectorOutputPayload response parameter will have a value similar to the following:
[{"AttributeName":"_op","AttributeValue":"ldapadoGetAttributes"},{"AttributeName":"usncreated","AttributeValue":"36006"},{"AttributeName":"countrycode","AttributeValue":"0"},{"AttributeName":"badpwdcount","AttributeValue":"0"},{"AttributeName":"dn","AttributeValue":""},{"AttributeName":"dn","AttributeValue":"CN=Bangalore user,OU=Bangalore,OU=India,OU=Domain_Users,DC=test-ldap,DC=com"},{"AttributeName":"whenchanged","AttributeValue":"20230913125155.0Z"},{"AttributeName":"objectclass","AttributeValue":"top"},{"AttributeName":"objectclass","AttributeValue":"person"},{"AttributeName":"objectclass","AttributeValue":"organizationalPerson"},{"AttributeName":"objectclass","AttributeValue":"user"},{"AttributeName":"primarygroupid","AttributeValue":"513"},{"AttributeName":"givenname","AttributeValue":"Bangalore"},{"AttributeName":"dscorepropagationdata","AttributeValue":"16010101000001.0Z"},{"AttributeName":"sn","AttributeValue":"user"},{"AttributeName":"useraccountcontrol","AttributeValue":"512"},{"AttributeName":"cn","AttributeValue":"Bangalore user"},{"AttributeName":"codepage","AttributeValue":"0"},{"AttributeName":"accountexpires","AttributeValue":"9223372036854775807"},{"AttributeName":"userprincipalname","AttributeValue":"user-1@test-l }]
Example - Add users to a group
- In the
Configure connector taskdialog, clickActions. - Select the
AddMembersToGroupaction, and then clickDone. - In theTask Input section of theConnectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{"GroupId":"1|CN=Cert Publishers,CN=Users,DC=test-ldap,DC=com","UserDNs":"[{\"DN\":\"CN=Google AI,CN=Users,DC=test-ldap,DC=com;CN=Guest,CN=Users,DC=test-ldap,DC=com\"}]"}
This example adds a user DN to the group with ID1|CN=Cert Publishers,CN=Users,DC=test-ldap,DC=com. If the action is successful, your connector task'sconnectorOutputPayload response parameter will have a value similar to the following:
[{"Success":"True"}]
Entity operation examples
Example - List users
This example lists all the users in theUser entity.
- In the
Configure connector taskdialog, clickEntities. - Select
Userfrom theEntitylist. - Select the
LISToperation, and then clickDone. - Optionally, you can filter the result set. To filter the result set, in theTask Input section of theConnectors task, set thefilterClause as per your requirement.
For example, setting the filter clause to
Id='1|CN=admin,CN=Users,DC=test-ldap,DC=com', lists only those records whose Id matches this criteria.
Example - Get a user record
This example gets a user detail from theUser entity.
- In the
Configure connector taskdialog, clickEntities. - Select
Userfrom theEntitylist. - Select the
GEToperation, and then clickDone. - In theTask Input section of theConnectors task, clickEntityId and then enter
1|CN=admin,CN=Users,DC=test-ldap,DC=comin theDefault Value field.Here,
1|CN=admin,CN=Users,DC=test-ldap,DC=comis one of the primary key values of theUserentity.
Example - Create a user record
This example creates a user record in theUser entity.
- In the
Configure connector taskdialog, clickEntities. - Select
Userfrom theEntitylist. - Select the
Createoperation, and then clickDone. - In theTask Input section of theConnectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{"RDN":"CN=MPATAI","ObjectClass":"top;person;organizationalPerson;user"}
If the integration is successful, your connector task's
connectorOutputPayloadfield will have a value similar to the following:{"Id":"1|CN=MPATAI,CN=Users,DC=test-ldap,DC=com"}
Example - Update a ticket
This example updates the specified user record in theUser entity.
- In the
Configure connector taskdialog, clickEntities. - Select
Userfrom theEntitylist. - Select the
Updateoperation, and then clickDone. - In theTask Input section of theConnectors task, click
connectorInputPayloadand then enter a value similar to the following in theDefault Valuefield:{"PostalCode":"560040"}
- ClickentityId, and then enter
1|CN=admin,CN=Users,DC=test-ldap,DC=comin theDefault Value field.Alternately, instead of specifying theentityId, you can also set thefilterClause to
1|CN=admin,CN=Users,DC=test-ldap,DC=com.If the integration is successful, your connector task's
connectorOutputPayloadfield will have a value similar to the following:{"Id":"1|CN=admin,CN=Users,DC=test-ldap,DC=com"}
Example - Delete a user record
This example deletes a user record from theUser entity.
- In the
Configure connector taskdialog, clickEntities. - Select
Userfrom theEntitylist. - Select the
Deleteoperation, and then clickDone. - In theTask Input section of theConnectors task, clickentityId and then enter
1|CN=admin,CN=Users,DC=test-ldap,DC=comin theDefault Value field. - Alternately, if
Userentity has composite primary keys, instead of specifying theentityId, you can set thefilterClause. For example,Id='1|CN=admin,CN=Users,DC=test-ldap,DC=com' and DN='CN=admin,CN=Users,DC=test-ldap,DC=com'.
Create connections using Terraform
You can use theTerraformresource to create a new connection.
To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.
To view a sample terraform template for connection creation, seesample template.
When creating this connection by using Terraform, you must set the following variables in your Terraform configuration file:
| Parameter name | Data type | Required | Description |
|---|---|---|---|
| base_dn | STRING | True | The base portion of the distinguished name, used for limiting results to specific subtrees. |
| auth_mechanism | ENUM | True | The authentication mechanism to be used when connecting to the LDAP server. Supported values are: SIMPLE, DIGESTMD5, NEGOTIATE |
| follow_referrals | BOOLEAN | False | Whether or not to follow LDAP referrals returned by the LDAP server. |
| friendly_guid | BOOLEAN | False | Whether to return GUID attribute values in a human readable format. |
| friendly_sid | BOOLEAN | False | Whether to return SID attribute values in a human readable format. |
| ldapversion | ENUM | True | The LDAP version used to connect to and communicate with the server. Supported values are: 2, 3 |
| scope | ENUM | True | Whether to limit the scope of the search to the whole subtree (BaseDN and all of its descendants), a single level (BaseDN and its direct descendants), or the base object (BaseDN only). Supported values are: WHOLESUBTREE, SINGLELEVEL, BASEOBJECT |
Use the LDAP connection in an integration
After you create the connection, it becomes available in bothApigee Integration and Application Integration. You can use the connectionin an integration through the Connectors task.
- To understand how to create and use the Connectors task in Apigee Integration, seeConnectors task.
- To understand how to create and use the Connectors task in Application Integration, seeConnectors task.
Get help from the Google Cloud community
You can post your questions and discuss this connector in the Google Cloudcommunity atCloud Forums.What's next
- Understand how tosuspend and resume a connection.
- Understand how tomonitor connector usage.
- Understand how toview connector logs.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-19 UTC.