node-ldapjs: The search fails if the DN string of base contains non-ascii characters.

Thank you for providing a reproduction showing the full search options used. A failing test has been added in #938.

This issue should be resolved in https://github.com/ldapjs/node-ldapjs/releases/tag/v3.0.5. Please open a new issue if this is not the case.

If this fix has helped you out, please consider contributing to my GitHub sponsorship.

The issue is https://github.com/ldapjs/filter/issues/6.

I appreciate the failing case as well since I was unable to generate one with the test server but could with production servers. Thanks @jimmyengman

As #936 was a duplicate of this issue I write my question here instead.

If I start an OpenLDAP docker container as suggested in https://github.com/ldapjs/docker-test-openldap and then connect to it with ldap.createClient (http://ldapjs.org/client.html) I can search with filter sn=Conrad and get a searchEntry for Hermes Conrad printed but when I search for sn=Rodríguez no entry is found.

It seems to work to have non ascii characters for some attributes (a group objects member attribute and objects entryDN attribute) but for all the rest I have tested it does not work. It is a problem because the swedish letter å,ä,ö are in many users and groups names and after upgrading to ldapjs v.3 we can no longer get a search result for them.

import { default as ldap } from 'ldapjs';

// ************ using this opts searching for user on surname no entry is found *****************
const opts = {
filter: '(&(sn=Rodríguez))',
scope: 'sub',
attributes: ['dn', 'sn', 'cn'],
type: 'user'
};

// ************ if this opts searching for user on surname are used an entry will be printed ************
// const opts = {
// filter: '(&(sn=Conrad))',
// scope: 'sub',
// attributes: ['dn', 'sn', 'cn'],
// type: 'user'
// };

// ************ if this opts are used an entry will be printed ************
// const opts = {
//   filter: '(&(entryDN=cn=Bender Bending Rodríguez,ou=people,dc=planetexpress,dc=com))',
//   scope: 'sub',
//   attributes: ['dn', 'sn', 'cn'],
//   type: 'user'
// };

// ************ if this opts are used an entry with the group ship_crew will be printed ************
// const opts = {
//   filter: '(&(member=cn=Bender Bending Rodríguez,ou=people,dc=planetexpress,dc=com))',
//   scope: 'sub',
//   attributes: ['dn', 'sn', 'cn'],
//   type: 'group'
// };

client.search('dc=planetexpress,dc=com', opts, (err, res) => {

res.on('searchRequest', (searchRequest) => {
console.log('searchRequest: ', searchRequest.messageId);
});
res.on('searchEntry', (entry) => {
console.log('entry: ' + JSON.stringify(entry.pojo));
});
res.on('searchReference', (referral) => {
console.log('referral: ' + referral.uris.join());
});
res.on('error', (err) => {
console.error('error: ' + err.message);
});
res.on('end', (result) => {
console.log('status: ' + result.status);
});
});

I really apologize for that mistake. I have closed the issue. I got the tests running in your repo.

I have a test written that (I believe) simulates my issue here, and the test is passing in the repo. I am searching for the group ‘ship_crew’ and then subsequently searching for each member via the DN that is returned in the member array. That group has a member (Bender Bending Rodríguez) that should simulate the issue we are seeing perfectly. I am not sure why our search is failing now, but I am going back there to see if I can find the issue in our code.

I believe I may be seeing the same issue here when trying to migrate our code to 3.x.

I have a DN that I retrieve from a group (in the member attribute). I need to then search for that DN to get the details.

For example, the DN returned in the member attribute is: “CN=Céline Jones,OU=Users,OU=France,DC=emea,DC=FOO,DC=com”

In v2.x, I could use that in a search as the “base” (scope: “base”) and I could find the user. In 3.0, that fails with “No Such Object”.

I tried creating a DN object (via parseDN(“CN=Céline Jones,OU=Users,OU=France,DC=emea,DC=FOO,DC=com”) and then using the “toString()” version of that in a search. That also fails.

In that case, the results of the DN.toString() are: “CN=C\c3\a9line Jones,OU=Users,OU=France,DC=emea,DC=FOO,DC=com” which looks correct.

As it stands, I cannot find a successful way to search for a DN with non-ASCII characters. I will research the document linked above more carefully, but these searches were working in v2.x.

I do not have access to the server at this time. So, I executed the following code. The string specified after “ou=” will be the same as the actual string.

const parseDN = require('ldapjs').parseDN;

const base = 'ou=テスト,dc=example,dc=com';
// "テスト" is the Japanese word for "test".

const baseDN = parseDN(base);

console.log(base);              // ou=テスト,dc=example,dc=com
console.log(baseDN.toString()); // ou=\e3\83\86\e3\82\b9\e3\83\88,dc=example,dc=com