Authenticates an LDAP connection using a distinguished name and password. This guide demonstrates its use in PHP code and explains when the result or side effect needs extra checks.
What It Does
Authenticates an LDAP connection using a distinguished name and password.
Syntax and Parameters
The examples below show a real call to ldap_bind with suitable arguments. Read the function call in context: its connection, handle, input data or other prerequisites are created before use.
Requirements: LDAP extension; an LDAPS directory and scoped credentials.
These examples are for an isolated development environment. Hostnames, credentials and remote paths must be replaced with your approved configuration.
Example 1: Core Behavior
Bind to a controlled directory and use a restricted service identity.
<?php
$user = getenv('LDAP_BIND_DN'); $pass = getenv('LDAP_PASSWORD');
if (!$user || !$pass) throw new RuntimeException('LDAP credentials are required');
$ldap = ldap_connect('ldaps://directory.internal.test:636');
if (!$ldap) throw new RuntimeException('LDAP handle unavailable');
ldap_set_option($ldap, LDAP_OPT_PROTOCOL_VERSION, 3);
$base = 'ou=People,dc=example,dc=test';
$dn = 'cn=Demo User,ou=People,dc=example,dc=test';
$filterValue = 'Alice (QA)';
$filter = '(cn=' . ldap_escape($filterValue, '', LDAP_ESCAPE_FILTER) . ')';
$resultValue = ldap_bind($ldap, $user, $pass);
echo is_bool($resultValue) ? ($resultValue ? "true" : "false") : json_encode($resultValue, JSON_PARTIAL_OUTPUT_ON_ERROR);
Observe the returned value or changed resource state. A successful function call can still require additional checks before a higher-level operation is considered successful.
Example 2: Alternative or Failure Case
The second example uses a different directory record or input value.
<?php
$user = getenv('LDAP_BIND_DN'); $pass = getenv('LDAP_PASSWORD');
if (!$user || !$pass) throw new RuntimeException('LDAP credentials are required');
$ldap = ldap_connect('ldaps://directory.internal.test:636');
if (!$ldap) throw new RuntimeException('LDAP handle unavailable');
ldap_set_option($ldap, LDAP_OPT_PROTOCOL_VERSION, 3);
$base = 'ou=People,dc=example,dc=test';
$dn = 'cn=Example Staff,ou=People,dc=example,dc=test';
$filterValue = 'Alice (QA)';
$filter = '(cn=' . ldap_escape($filterValue, '', LDAP_ESCAPE_FILTER) . ')';
ldap_set_option($ldap, LDAP_OPT_NETWORK_TIMEOUT, 5);
$resultValue = ldap_bind($ldap, $user, $pass);
echo is_bool($resultValue) ? ($resultValue ? "true" : "false") : json_encode($resultValue, JSON_PARTIAL_OUTPUT_ON_ERROR);
Compare the different inputs, environment assumptions or result checks. Do not use a transport-level success value as proof that all business-level requirements were met.
Practical Example: Applying the Rule
Check permissions, server controls and returned result types before modifying live directory data.
<?php
$user = getenv('LDAP_BIND_DN'); $pass = getenv('LDAP_PASSWORD');
if (!$user || !$pass) throw new RuntimeException('LDAP credentials are required');
$ldap = ldap_connect('ldaps://directory.internal.test:636');
if (!$ldap) throw new RuntimeException('LDAP handle unavailable');
ldap_set_option($ldap, LDAP_OPT_PROTOCOL_VERSION, 3);
$base = 'ou=People,dc=example,dc=test';
$dn = 'cn=Test Member,ou=People,dc=example,dc=test';
$filterValue = 'Alice (QA)';
$filter = '(cn=' . ldap_escape($filterValue, '', LDAP_ESCAPE_FILTER) . ')';
ldap_set_option($ldap, LDAP_OPT_NETWORK_TIMEOUT, 6);
$resultValue = ldap_bind($ldap, $user, $pass);
echo is_bool($resultValue) ? ($resultValue ? "true" : "false") : json_encode($resultValue, JSON_PARTIAL_OUTPUT_ON_ERROR);
In an application, convert low-level failures into controlled responses and log only non-sensitive diagnostic context.
Important Behavior and Edge Cases
Bind credentials require TLS; an empty password can trigger unintended anonymous behavior.
LDAP filter values and DN values require different escaping flags. Never concatenate unchecked user input into a directory query.
Comparison with Related Functions or Patterns
| Approach | When it differs |
|---|---|
| ldap_bind | Authenticates an LDAP connection using a distinguished name and password. |
| Related API or pattern | ldap_sasl_bind supports SASL authentication mechanisms when installed. |
Common Beginner Mistakes
| Mistake | Correct approach |
|---|---|
| Assuming a connection handle is already authenticated or encrypted | Bind credentials require TLS; an empty password can trigger unintended anonymous behavior. |
| Substituting a related API without checking its semantics | ldap_sasl_bind supports SASL authentication mechanisms when installed. |
Key Takeaways
- Authenticates an LDAP connection using a distinguished name and password.
- Bind credentials require TLS; an empty password can trigger unintended anonymous behavior.
- ldap_sasl_bind supports SASL authentication mechanisms when installed.
Select this API or pattern based on its documented behavior and the trust boundaries in your own application, and test all external integrations against their actual deployments.