v1.3.0

What's Changed

• Update controls dependency to include PasswordPolicyControl by @its-sami in #8
• Allow for AD range attribute option by @chastabor in #9

New Contributors

• @its-sami made their first contribution in #8
• @chastabor made their first contribution in #9

Full Changelog: v1.2.1...v1.3.0

v1.2.1

What's Changed

• Update dependencies by @jsumners in #7

Full Changelog: v1.2.0...v1.2.1

v1.1.1

What's Changed

• Fix documentation of dn property by @simon-lorenz in #5

New Contributors

• @simon-lorenz made their first contribution in #5

Full Changelog: v1.1.0...v1.1.1

v1.1.0

Important: this release will generate process warning when a search entry object encounters an empty attribute name. Empty attribute names are not spec compliant. See ldapjs/node-ldapjs#867 for more details.

What's Changed

• skip attribute with empty name by @ahaenggli in #4

New Contributors

• @ahaenggli made their first contribution in #4

Full Changelog: v1.0.2...v1.1.0

v1.0.2

What's Changed

• Allow single character attribute names by @jsumners in #3

Full Changelog: v1.0.1...v1.0.2

v1.0.1

SearchRequest.scope now returns the associated LDAP scope code instead of a name. SearchRequest.scopeName has been added to facilitate getting a friendly name for the search scope. There is an argument to be made for this being a breaking change, but we see it as a correction in behavior. The .scope is used for matching in search requests when writing an LDAP server. So scopes should able to easily be checked against the exported scope constants (RFC defined constants).

What's Changed

• Fix SearchRequest scope property by @jsumners in #1

New Contributors

• @jsumners made their first contribution in #1

Full Changelog: v1.0.0...v1.0.1

v1.0.0

Initial release.