Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

LDAP and Active Directory

LDAP - Create User Node

search

Please Note:

LDAP - Create User Node

   
Description The LDAP - Create User node creates a new user entry in the LDAP directory using the provided configuration and attributes.
Available in Authentication, Admin, Self Service, API, Consent, Library, Custom, User Defined
Node Name LDAP - Create User

LDAP Configuration

Connection Mode Defines the connection protocol used to communicate with the LDAP server. Option available: - **ldap**: Standard (non-secure) connection (port 389). - **ldaps**: Secure connection over SSL/TLS (port 636). - **start-tls**: Connection starts as a standard LDAP connection (typically on port 389) and is then upgraded to a secure channel using TLS.
Hostname Specifies the **hostname** or **IP address** of the LDAP server.
Port Defines the port used to connect to the LDAP server. Typical values: - **389** for LDAP - **636** for LDAPS
Connection Timeout Specifies the maximum time (in seconds) to wait for a connection to the LDAP server. A value of 0 usually means **no timeout**.
Admin user DN The **Distinguished Name (DN)** of the administrative user used to perform the LDAP search operation.
Admin user Password The password associated with the **admin user DN**.
Base DN Defines the **base context (starting point)** in the LDAP directory where the user search will be performed.
Search Scope Defines the scope of the LDAP search: - **base**: Searches only the base DN - **one**: Searches one level under the base DN - **sub**: Searches the entire subtree under the base DN
User DN Specifies the Distinguished Name (DN) of the **user to be created**. This uniquely identifies the user within the **LDAP directory** and defines its position in the directory tree. The value can be dynamically constructed using variables from the flow. Example: `uid={{username}},ou=users,dc=example,dc=com`
Object Class Defines the set of **object classes assigned** to the new LDAP entry. Object classes determine which attributes the user can or must have. **Multiple object classes can be specified** depending on the LDAP schema. Example: `inetOrgPerson` `organizationalPerson` `person` `top`

Node Configuration

User Mapping This section allows you to define the **mapping** between **Monokee user attributes** and the **corresponding values** while modifying / updating the user. Each value can be assigned a static value or **dynamically populated** using variables returned by previous nodes in the flow (e.g `{{form.username}}` and `{{form.password}}`). Rule are defined as: `Monokee attribute : value retrieved from the node` Example: `username: {{uid}}` `name: {{givenName}}` #### Attribute Manipulation It is possible to use a set of basic functions to manipulate values, see [Attribute Manipulation]({filename}/pages/io/io-nodes/io-node-types/common-configurations.md#attribute-manipulation).

Default Output Node

  • Success
  • Entry Already Exists
  • Invalid Syntax
  • Object Class Violation
  • Failure

On this page