LDAP probe
The LDAP probe sends a sequence of LDAP operations to a directory server. VirtuProbe implements the LDAP protocol from scratch (BER encoding, RFC 4511) — no third-party LDAP library is used, giving full control for testing and fuzzing.
[SCREENSHOT: LDAP probe editor — host/port/LDAPS settings, operation list]
Connection settings
Section titled “Connection settings”| Field | Description |
|---|---|
| Host | LDAP server hostname or IP |
| Port | Server port (common: 389, 636) |
| LDAPS | Connect with SSL (port 636) |
Operations
Section titled “Operations”| Operation | Description |
|---|---|
BIND | Authenticate with a DN and password |
SEARCH | Search the directory with a filter |
UNBIND | Close the session |
DELETE | Remove an entry by DN |
COMPARE | Test whether an entry has a given attribute value |
[SCREENSHOT: BIND operation form — DN and password fields]
| Field | Description |
|---|---|
| DN | Distinguished name to bind as (e.g. cn=admin,dc=example,dc=com) |
| Password | Bind password |
SEARCH
Section titled “SEARCH”[SCREENSHOT: SEARCH operation form — base DN, scope, filter, attributes, size/time limits]
| Field | Description |
|---|---|
| Base DN | Search root |
| Scope | BASE, ONE, or SUB |
| Filter | RFC 4515 filter string (e.g. (uid=jdoe), (&(objectClass=person)(cn=*))) |
| Attributes | Comma-separated list of attributes to return (blank = all) |
| Size limit | Maximum number of entries to return |
| Time limit | Maximum server processing time in seconds |
Supported filter syntax: equality (cn=John), presence (cn=*), substring (cn=J*), >=, <=, and (&...), or (|...), not (!...).
COMPARE
Section titled “COMPARE”| Field | Description |
|---|---|
| DN | Entry to compare against |
| Attribute | Attribute name |
| Value | Value to compare |
Assertions
Section titled “Assertions”Set an expected result code on any operation. Standard LDAP result codes: 0 (success), 32 (no such object), 49 (invalid credentials), etc. If the actual code differs, the history entry is marked as failed.
[SCREENSHOT: LDAP operation with failed assertion — warning chip showing expected vs actual result code]
Variable substitution
Section titled “Variable substitution”{{variable}} placeholders are supported in: host, DN, password, filter, attribute, and value fields.
History
Section titled “History”The history panel shows the result code and exchange data for each operation.
[SCREENSHOT: LDAP history panel — expanded entry showing per-operation result codes]