The Blink platform enables you to perform actions using the Lightweight Directory Access Protocol.

​
Creating an LDAP connection

In order to create a connection to an LDAP server, you must have it exposed to your Blink Runner.

By default, Blink will connect over port 389 for LDAP or port 636 for LDAPS.

If using secure LDAP, the certificate must be generated by a valid certificate authority and not self-signed.

​
Creating your connection

  1. In the Blink platform, navigate to the Connections page > Add connection. A New Connection dialog box opens displaying icons of external service providers available.

  2. Select the LDAP icon. A dialog box with name of the connection and connection methods appears.

  3. (Optional) Edit the name of the connection. At a later stage you cannot edit the name.

  4. Select LDAP as the method to create the connection.

  5. Fill in the parameters:

    • The URI for your LDAP server host, including the protocol (either ldap:// or ldaps://) and optionally a port number.

    • The DN (Distinguished Name) to connect as.

    • Password to use for authentication. Leave this blank if the server supports unauthenticated access.

    • Which LDAP Protocol version to use. If left empty, Blink will negotiate with the server to choose the best supported version.

    • Which Distinguished Name to search from. This can be interpreted as the “root path” of the directory to connect to, while the dn parameter is the “username”.

      Can also be overridden per search.

      If left empty, the server chooses the default.

    • Ignore Certificate Validation - Whether certificate should be ignored or validated.

  6. (Optional) Click Test Connection to test it.

  7. Click Create connection. The new connection appears on the Connections page.

​
Actions

Opens a connection to an LDAP server, binds, and performs a search using specified parameters.

For more information, view the Linux documentation.

ParameterDescription
FiltersLDIF style search filter.
BaseIf left empty, the one specified in the connection will be used, otherwise the server will choose the default.
AttributesComma-separated list of attributes to return. Put ”*” for all attributes.
ScopeSpecify the scope of the search to be one of base, one, or sub to specify a base object, one-level, or subtree respectively.

​
LDAP Add

Opens a connection to an LDAP server, binds, and adds entries.

For more information, view the Linux documentation.

ParameterDescription
CodeA series of LDIF-format entries to add.

​
LDAP Modify

Opens a connection to an LDAP server, binds, and modifies entries.

For more information, view the Linux documentation.

ParameterDescription
CodeA series of LDIF-format modification commands.

​
LDAP Delete

Opens a connection to an LDAP server, binds, and deletes entries.

For more information, view the Linux documentation.

ParameterDescription
Distinguished NamesA line-separated series of Distinguished Names to delete, in LDAPv3 string representation.
Recursive DeleteDo a recursive delete. If the DN specified isn’t a leaf: it’s children, and all their children are deleted down the tree. No verification is done, so if you add this switch, LDAP Delete will delete large portions of your tree. Use with caution.

The Blink platform enables you to perform actions using the Lightweight Directory Access Protocol.

​
Creating an LDAP connection

In order to create a connection to an LDAP server, you must have it exposed to your Blink Runner.

By default, Blink will connect over port 389 for LDAP or port 636 for LDAPS.

If using secure LDAP, the certificate must be generated by a valid certificate authority and not self-signed.

​
Creating your connection

  1. In the Blink platform, navigate to the Connections page > Add connection. A New Connection dialog box opens displaying icons of external service providers available.

  2. Select the LDAP icon. A dialog box with name of the connection and connection methods appears.

  3. (Optional) Edit the name of the connection. At a later stage you cannot edit the name.

  4. Select LDAP as the method to create the connection.

  5. Fill in the parameters:

    • The URI for your LDAP server host, including the protocol (either ldap:// or ldaps://) and optionally a port number.

    • The DN (Distinguished Name) to connect as.

    • Password to use for authentication. Leave this blank if the server supports unauthenticated access.

    • Which LDAP Protocol version to use. If left empty, Blink will negotiate with the server to choose the best supported version.

    • Which Distinguished Name to search from. This can be interpreted as the “root path” of the directory to connect to, while the dn parameter is the “username”.

      Can also be overridden per search.

      If left empty, the server chooses the default.

    • Ignore Certificate Validation - Whether certificate should be ignored or validated.

  6. (Optional) Click Test Connection to test it.

  7. Click Create connection. The new connection appears on the Connections page.

​
Actions

Opens a connection to an LDAP server, binds, and performs a search using specified parameters.

For more information, view the Linux documentation.

ParameterDescription
FiltersLDIF style search filter.
BaseIf left empty, the one specified in the connection will be used, otherwise the server will choose the default.
AttributesComma-separated list of attributes to return. Put ”*” for all attributes.
ScopeSpecify the scope of the search to be one of base, one, or sub to specify a base object, one-level, or subtree respectively.

​
LDAP Add

Opens a connection to an LDAP server, binds, and adds entries.

For more information, view the Linux documentation.

ParameterDescription
CodeA series of LDIF-format entries to add.

​
LDAP Modify

Opens a connection to an LDAP server, binds, and modifies entries.

For more information, view the Linux documentation.

ParameterDescription
CodeA series of LDIF-format modification commands.

​
LDAP Delete

Opens a connection to an LDAP server, binds, and deletes entries.

For more information, view the Linux documentation.

ParameterDescription
Distinguished NamesA line-separated series of Distinguished Names to delete, in LDAPv3 string representation.
Recursive DeleteDo a recursive delete. If the DN specified isn’t a leaf: it’s children, and all their children are deleted down the tree. No verification is done, so if you add this switch, LDAP Delete will delete large portions of your tree. Use with caution.