Releases: ldapjs/node-ldapjs
v3.0.7
v3.0.6
v3.0.5
v3.0.4
v3.0.3
What's Changed
- build(deps-dev): bump eslint from 8.36.0 to 8.37.0 by @dependabot in #866
- build(deps-dev): bump eslint from 8.37.0 to 8.38.0 by @dependabot in #869
- build(deps-dev): bump eslint from 8.38.0 to 8.39.0 by @dependabot in #875
- build(deps): bump @ldapjs/messages from 1.0.2 to 1.1.0 by @dependabot in #874
- build(deps): bump @ldapjs/dn from 1.0.0 to 1.1.0 by @dependabot in #879
- build(deps-dev): bump eslint from 8.39.0 to 8.40.0 by @dependabot in #881
- Add paged searching test by @jsumners in #886
- Address issue #883 by @jsumners in #884
- build(deps-dev): bump eslint-plugin-n from 15.7.0 to 16.0.0 by @dependabot in #889
- build(deps-dev): bump eslint from 8.40.0 to 8.41.0 by @dependabot in #888
- build(deps-dev): bump eslint from 8.41.0 to 8.42.0 by @dependabot in #896
- update modification object in ldap.change by @mihir254 in #910
- Address crash for unmatched server responses by @jsumners in #913 (thank you to @benzhuo and @michelevince for aiding in resolving this issue)
- Update minimum dependencies by @jsumners in #916
New Contributors
Full Changelog: v3.0.2...v3.0.3
v3.0.2
What's Changed
- build(deps-dev): bump eslint from 8.35.0 to 8.36.0 by @dependabot in #851
- build(deps): bump @ldapjs/messages from 1.0.1 to 1.0.2 by @dependabot in #852
- Add test for issue 860 by @jsumners in #861
- transcontextual safe type checks by @axkibe in #864
New Contributors
Full Changelog: v3.0.1...v3.0.2
v3.0.1
What's Changed
- build(deps-dev): bump eslint from 8.34.0 to 8.35.0 by @dependabot in #844
- Quick fix for outdated client doc still referring to result.object by @Tethik in #846
- Resolve issue #845 by @jsumners in #847
- Add Node.js version support to readme by @jsumners in #848
Full Changelog: v3.0.0...v3.0.1
v3.0.0
🎉🎉🎉 Version 3.0.0 Is Here
This release has been in development for many months. The first commit toward this goal happened on 2019-09-01, but work really started with a commit on 2022-03-27.
This is not a trivial release. There are significant changes under the hood. They include:
- Common modules have been broken out into separate installable modules:
@ldapjs/attribute
-- a comprehensive implementation of the LDAPattribute
spec.@ldapjs/change
-- a full implementation of RFC 4511 §4.6.@ldapjs/controls
-- specific implementations for all supported controls (with a caveat detailed below) that inherit from a base identifiable object.@ldapjs/dn
-- providesDN
andRDN
objects to represent LDAP distinguished names.@ldapjs/messages
-- all supported messages as their own objects with methods and properties matching the specs, including a complete overhaul of theextension
(renamed fromextended
) request and response objects (with added support for several extensions, e.g. "password modify").@ldapjs/protocol
-- now with a full suite of operation identifiers, result codes, and search tags.
ldap-filter
has been forked to@ldapjs/filter
. It includes improvements around value escaping, modern method signatures, and identifiable "class" objects. The full set of changes can be reviewed at ldapjs/filter@daa5a5d...v2.0.0asn1
has been forked to@ldapjs/asn1
. Methods have been improved, e.g.BerReader.readBoolean
now accepts a tag to expect, new ones added, e.g.BerWriter.appendBuffer
, unreachable code removed, and bugs fixed. The full set of changes can be reviewed at ldapjs/asn1@bf1bb90...v2.0.0
Additionally, all of the above modules now have complete, 100%, test coverage (except for @ldapjs/filter
; PRs are welcome to help out here). They are also comprehensively documented with jsdoc.
We expect there are going to be issues with this release. We worked hard to make sure all of the current tests pass without any changes (or at least none that affect the purpose of the test). But the current test suite is by no means comprehensive, and such sweeping changes as are present in this release are almost guaranteed to introduce new bugs. Please bear with us as we resolve them. Your contributions to fix any such bugs will help greatly.
Even the simple act of opening an issue describing something you've found that should be in these release notes would be a big help. For example, if you have determined that a change in some object API, e.g. the SearchRequest
object, should be highlighted, then please open an issue describing the change so that we can add an it to an addendum on these release notes.
The Biggest Change
We think that the most impactful change is going to be the decoupling of the underlying byte arrays from all objects. In v2 and earlier, the client, server, controls, messages, and everything else passed around single byte arrays during the handling of requests. The benefit of this is reduced memory consumption and faster handling of requests. The downside is an extremely difficult to understand and maintain codebase. As part of the work to modularize this codebase, we opted to make byte array processing idempotent in the majority of cases. This will have an impact on performance, but we do not know how much of an impact. We do not have any way to benchmark the before and after of this change. We suspect (hope) that in the majority of cases it will not be noticeable.
VLV Controls
During the development of v3 we were not clear if the VLV implementation that was added to v2 was correct. So we opted to cut it for the release. Shortly after cutting it, we determined that the implementation is very likely correct. You can read about this decision at #797 (comment) and the realization at #797 (comment).
Ultimately, we decided to postpone adding this feature back so that we could get v3 shipped.
Conclusion
A lot of hard work has gone into this release. We think it lays the ground work for a much more maintainable codebase. We envision being able to re-implement the server and client components as @ldapjs/server
and @ldapjs/client
at some point in the future. We think there is a real opportunity to refactor both components into more modern interfaces with significant improvements (particularly in the form of error handling). No promises are made about when such projects might be undertaken, if ever. But they wouldn't be possible without the work in this v3 release.
In regard to my (James Sumners) personal contributions to this release, please consider using my ❤️ GitHub Sponsor link to show your gratitude. Contributions will be particularly helpful at this time; I was laid off as part of a significant downsizing event at my previous employer and am currently unemployed.
Additionally, a big thank you to @dirmgr for his willingness to answer general LDAP protocol questions and the abundance of well written documentation he has provided at https://nawilson.com/ldapv3-wire-protocol-reference/ and https://ldap.com/learn-about-ldap/. The help and articles were indispensable in crafting this release.
Known Breaking Changes
Client
options.strictDN
: removed. All DN parsing is now "strict". It does not make any sense to try and parse DN strings that are not spec compliant..modify
: no longer accepts plain objects as change descriptors. An instance of@ldapjs/change
is now required.searchEntry
object: thesearchEntry
object no longe provides a.raw
property. The access this property provided is now supplied by thesearchEntry
object's standard methods and accessors, e.g..attributes
for the set of attributes returned on the entry. Further, accessing binary field values should be done by specifying the;binary
attribute option as per the LDAP spec. See #850 and #858 for more detail.- Change objects: generic JavaScript objects are no longer supported as
change
objects. When creating a newchange
object,@ldapjs/attribute
objects must be provided (or a plain object that conforms to anattribute
object). See #859 for more detail.
Server
options.strictDN
: removed. All DN parsing is now "strict". It does not make any sense to try and parse DN strings that are not spec compliant..listen
: No longer listens on0.0.0.0
when nohost
parameter is provided. It now uses the secure default of127.0.0.1
..search
: the results ofSearchRequest.scope
changed to the spec defined search scope names. Withldapjs@3.0.0
(and@ldapjs/messages@1.0.0
) you must match againstbase
,single
, andsubtree
instead ofbase
,one
, andsub
. This has been corrected inldapjs@3.0.1
(with@ldapjs/messages@1.0.1
) via PR #847. See the unit test included in that release for the recommended approach for matching search scopes.
General
- Message objects no longer have a
.object
accessor. This has been replaced with the.pojo
accessor. It didn't make any sense to have a message object with an accessor that returns an object (it's confusing). The.pojo
accessor states what will be returned: a plain JavaScript object. You may find that the actual message object now has fields you can directly use. See #841. - Filter strings no longer provide a static exception on case sensitive comparisons for
objectClass
. Inldapjs@2
and earlier, there were many explicit checks forobjectClass
being compared. When such a comparison was found, the code always performed that specific comparison in a case insensitive manner. As ofldapjs@3
, you must specify that you want to perform case insensitive comparisons on property names. See ldapjs/filter#3 for more detail.
v2.3.3
What's Changed
- build(deps): bump actions/setup-node from 2.5.1 to 3 by @dependabot in #788
- build(deps): bump actions/checkout from 2 to 3 by @dependabot in #789
- build(deps-dev): bump tap from 15.1.6 to 15.2.2 by @dependabot in #790
- build(deps-dev): bump tap from 15.2.2 to 15.2.3 by @dependabot in #792
- Update docker config by @jsumners in #794
- Progress on supporting IPv6 by @MaxLeiter in #805
- v2.3.3 by @jsumners in #807
New Contributors
- @MaxLeiter made their first contribution in #805
Full Changelog: v2.3.2...v2.3.3
v2.3.2
What's Changed
- build(deps-dev): bump marked from 2.1.3 to 3.0.0 by @dependabot in #758
- build(deps): bump actions/setup-node from 2.3.0 to 2.4.0 by @dependabot in #757
- build(deps-dev): bump tap from 15.0.9 to 15.0.10 by @dependabot in #760
- build(deps): bump actions/setup-node from 2.4.0 to 2.4.1 by @dependabot in #762
- build(deps-dev): bump marked from 3.0.8 to 4.0.0 by @dependabot in #768
- build(deps-dev): bump tap from 15.0.10 to 15.1.2 by @dependabot in #771
- build(deps-dev): bump tap from 15.1.2 to 15.1.5 by @dependabot in #772
- build(deps): bump actions/setup-node from 2.4.1 to 2.5.0 by @dependabot in #774
- build(deps): bump actions/setup-node from 2.5.0 to 2.5.1 by @dependabot in #777
- build(deps-dev): bump tap from 15.1.5 to 15.1.6 by @dependabot in #780
- Add Note on Client Error Handling to Documentation by @FabianScheidt in #786
- force socket to be closed on destroy by @dfit99 in #785
- v2.3.2 by @jsumners in #787
New Contributors
- @FabianScheidt made their first contribution in #786
- @dfit99 made their first contribution in #785
Full Changelog: v2.3.1...v2.3.2