Integrations
Set up LDAP credentials in Duaer
Store LDAP connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
Connect to LDAP
The Duaer LDAP credential:
- LDAP Server Address is the server’s IP or domain.
- Match Connection Security and port: usually 389 for None and STARTTLS, and 636 for TLS (LDAPS).
- Binding DN is the account to sign in with, such as cn=admin,dc=example,dc=com. Active Directory also accepts a UPN such as user@example.com. Binding Password is that account’s password.
- When an internal CA issued the server certificate, paste the CA certificate into CA Certificate.
Give the bind account the workflow uses rights only to search and to change the parts of the directory it needs.
LDAP fields in Duaer
In Duaer, choose LDAP when you create a credential, then fill in these fields:
- LDAP Server Address (required): IP or domain of the LDAP server.
- LDAP Server Port: Port used to connect to the LDAP server. Default: 389.
- Binding DN: Distinguished Name of the user to connect as.
- Binding Password (secret): Password of the user provided in the Binding DN field above.
- Connection Security: Default: None. Options: None, TLS, STARTTLS.
- Ignore SSL/TLS Issues: Whether to connect even if SSL/TLS certificate validation is not possible. Default: off.
- CA Certificate
- Timeout: Optional connection timeout in seconds. Default: 300.
Duaer nodes that use it: Ldap.
Save the connection in Duaer
Open Credentials and create LDAP. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.
Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. The matching node is under the related node.
Who can use this credential
Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
Questions
Do LDAP secret values appear in Duaer node parameters?
No. In Duaer, LDAP secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.
What usually stops a LDAP credential from saving in Duaer?
Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields LDAP expects, then confirm you can create credentials in that project.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.