corresponding field in v3 of the raw field in v2

[shaozi]

In v2, in ldap client search function, on searchEntry event callback, the entry parameter has a raw field:

ldapClient.search(searchBase, searchOptions, function (err, res) {
//...
  res.on('searchEntry', function (entry) {
        user = entry.object
        user.raw = object.raw
      })

What is the corresponding raw field in the new entry or entry.pojo in v3?

[jsumners]

It's not clear what the purpose of .raw is:

node-ldapjs/lib/messages/search_entry.js

Lines 64 to 88 in 92dfc80

	raw: {
	get: function getRaw () {
	const obj = {
	dn: this.dn.toString(),
	controls: []
	}
	this.attributes.forEach(function (a) {
	if (a.buffers && a.buffers.length) {
	if (a.buffers.length > 1) {
	obj[a.type] = a.buffers.slice()
	} else {
	obj[a.type] = a.buffers[0]
	}
	} else {
	obj[a.type] = []
	}
	})
	this.controls.forEach(function (element) {
	obj.controls.push(element.json)
	})
	return obj
	},
	configurable: false
	}

You should use the methods native to the SearchResultEntry object. See https://github.com/ldapjs/messages/blob/b37b2f5fe400d09deea47103f609a8c29a86452d/lib/messages/search-result-entry.js

[christopherpickering]

@jsumners raw was added to be able to get images through a buffer. See this issue #290

Is there a better way to get the image buffers?

[christopherpickering]

I went on a treasure hunt and found the answer :)
Adding a ;binary at the end of the attributes requested will give the correct base64 back and it doesn't need to be converted as we did w/ the .raw stuff.

https://github.com/ldapjs/attribute/blob/d1cba4723fb6953a932a71b53a8d842eeab564c7/index.js#L23

This seems to be a new features (at least I couldn't find it in v2) Thanks @jsumners :)

[jsumners]

How would you notate this change in the v3 release notes, @christopherpickering?

[christopherpickering]

.raw search entry property has been removed. It was used to access binary attribute data. Binary attributes can now be accessed by appending ;binary to the attribute name.

Hows that sound?

[jsumners]

I have updated the v3 release notes with this information.

[ghost]

While using searchEntry in v2 I was able to acces to the entry result like this:

res.on('searchEntry', async (entry: any) => {
             console.log("entry.dn ",entry.dn);
}

But in v3 I got an empty objcts instead of my fields, what do I need to change ?

[shaozi]

While using searchEntry in v2 I was able to acces to the entry result like this:

res.on('searchEntry', async (entry: any) => {
             console.log("entry.dn ",entry.dn);
}

But in v3 I got an empty objcts instead of my fields, what do I need to change ?

I believe in v3 the dn is entry.objectName