redb.Route.Ldap 4.2.2

redb.Route.Ldap

LDAP / Active Directory connector for redb.Route. Search, CRUD, authentication, and change tracking — all directory operations as endpoints via Novell.Directory.Ldap.NETStandard.

Installation

dotnet add package redb.Route.Ldap

Usage

URI Format

ldap:OPERATION:baseDn?server=host&port=389&bindDn=cn=admin,dc=example,dc=com&bindPassword=secret

Fluent DSL

using redb.Route.Ldap;

// Search users
From(Ldap.Search("ou=users,dc=example,dc=com")
        .Server("ldap.example.com")
        .BindDn("cn=admin,dc=example,dc=com")
        .BindPassword("secret")
        .Filter("(objectClass=inetOrgPerson)")
        .Scope(LdapSearchScope.Subtree)
        .Attributes("cn", "mail", "uid")
        .PageSize(500))
    .Log("Found: ${header['redbLdap.ResultCount']} entries")
    .To("direct://process");

// Watch for changes (consumer — polls for modifications)
From(Ldap.Watch("ou=users,dc=example,dc=com")
        .Server("ldap.example.com")
        .BindDn("cn=admin,dc=example,dc=com")
        .BindPassword("secret")
        .ChangeTracking(LdapChangeTrackingMode.ModifyTimestamp)
        .PollInterval(5000)
        .InitialLoad())
    .Log("Changed entry: ${body}")
    .To("direct://sync");

// Add entry
From("direct://create-user")
    .To(Ldap.Add("ou=users,dc=example,dc=com")
        .Server("ldap.example.com")
        .BindDn("cn=admin,dc=example,dc=com")
        .BindPassword("secret"));

// Modify entry
From("direct://update-user")
    .To(Ldap.Modify("cn=alice,ou=users,dc=example,dc=com")
        .Server("ldap.example.com")
        .BindDn("cn=admin,dc=example,dc=com")
        .BindPassword("secret"));

// Bind (authentication check)
From("direct://authenticate")
    .To(Ldap.Bind("dc=example,dc=com")
        .Server("ldap.example.com"));

Fluent Builder API

Most builder methods accept both constant values and IExpression for runtime resolution via the expression engine.

Exchange Headers

Change Tracking Modes

Docker (for testing)

services:
  openldap:
    image: osixia/openldap:1.5.0
    ports:
      - "389:389"
      - "636:636"
    environment:
      LDAP_ORGANISATION: "redb"
      LDAP_DOMAIN: "redb.test"
      LDAP_ADMIN_PASSWORD: "admin"

Part of

redb.Route — ESB & EIP Framework for .NET

Named connection factory

Keep credentials out of the route URI: register a factory in the context registry and reference it by name. A set-but-unknown name fails loud at startup — a typo can never silently fall back to inline URI parameters.

context.AddToRegistry("prod", new LdapConnectionFactory
{
    Server = "dc01.corp.local",
    BindDn = "CN=svc,OU=Service,DC=corp,DC=local",
    BindPassword = secrets.LdapPassword,
});
// ldap:SEARCH:dc=corp,dc=local?connectionFactory=prod

Tracing

On the redb.Route activity source (AddSource("redb.Route")), with network.protocol.name = ldap and redb.route.endpoint:

• Consumer (WATCH). One Consumer span, ldap {baseDn} receive, per routed entry. An entry carries no trace context, so the span is a root, never a child of the activity the poll loop inherited from whoever started the routes; a poll that finds nothing opens none. A failed route marks it an error, whether the failure stays on the exchange or escapes the pipeline; our own stop does not.
• Producer. One Client span per operation, ldap.{operation}, with the ldap.* tags; an error when the operation fails, unless our own token cancelled it. A rejected BIND is an answer, not a failure: it is on ldap.bind_result.
• RouteEngineOptions.EnableTelemetry = false opens neither span.