node-ldapjs: ldapjs can't handle a well known container query

To query for a well known container in Active Directory, you supply the query with a baseDN that’s formatted in an unusual way.

ldapjs fails when presented with this query:

node_modules/ldapjs/lib/dn.js:212
    if (beg === cur) { throw invalidDN(name) }
                       ^

Error [InvalidDistinguishedNameError]: <WKGUID=A9D1CA15768811D1ADED00C04FD8D5CD,dc=dmtest,dc=suse,dc=de>
    at invalidDN ( node_modules/ldapjs/lib/dn.js:8:13)
    at parseAttrType ( node_modules/ldapjs/lib/dn.js:212:30)
    at parseRdn ( node_modules/ldapjs/lib/dn.js:171:20)
    at Object.parse ( node_modules/ldapjs/lib/dn.js:290:13)
    at ensureDN ( node_modules/ldapjs/lib/client/client.js:85:15)
    at Client.search ( node_modules/ldapjs/lib/client/client.js:596:18)

About this issue

Original URL
State: closed
Created a year ago
Comments: 18 (6 by maintainers)

Most upvoted comments

Well, you should be able to get up and running with this command:

sudo docker run --privileged -p 53:53 -p 53:53/udp -p 88:88 -p 88:88/udp -p 123:123/udp -p 135:135 -p 137:137/udp -p 138:138/udp -p 139:139 -p 389:389 -p 389:389/udp -p 445:445 -p 464:464 -p 464:464/udp -p 636:636 -p 3268:3268 -p 3269:3269 registry.opensuse.org/opensuse/samba-ad-dc -p example.com:Test1234

You could probably just communicate with ldap via the container IP, and not mess with fixing dns.

dmulder on Feb 24, 2023