You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 14, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on May 14, 2024. It is now read-only.
There are open pull requests with no activity from @joyent. Is this project still maintained? If it is active, I apologize. If not, can it be transferred to an organization with members that will be active?
(Sorry, misread the URL earlier, and thought this was a different ticket. Posting new comment.)
@jgeurts Sorry for the lack of activity lately. I'd planned on taking care of them earlier this year when I transferred the repo, but I've had other things come up, and haven't had the time to fix things correctly. I'm hoping to work my way through them soon. Is there a specific ticket you were looking at?
No worries, I definitely understand how things come up, just didn't want the project to become abandoned. I'm mainly interested in #485. That is preventing us from updating to node v10.
Reacted by purplemana, Jeffrey D. Van Alstine and justin-scx
I'm not convinced this project is active anymore, unfortunately.
If anyone is interested, I have started working on the https://github.com/ldapts/ldapts project. The goal, aside from adding type information, is to modernize the syntax a bit and fix some outstanding issues.
It's still very early in development (I'm working on Client first) and I welcome anyone who wants to lend a hand...
If anyone needs node v10+ support, I've been using https://www.npmjs.com/package/ldapts for over a week to connect to a couple active directories with > 30k users. It has been working well and includes the fixes in #497.
Reacted by sunpeinju, purplemana and Martin Zaloudek
For those looking for a lightweight LDAP server protocol implementation, perhaps this (pure) PHP library is an option worth considering: https://github.com/FreeDSx/LDAP/blob/master/docs/Server/General-Usage.md
Besides that there is also a Go LDAP client/server implementation: glauth
But for web developers the PHP switch might be a closer call.
@melloc has responded June 22 2019 here: nodejs/package-maintenance#221
Currently at our work we are trying to make a choice for which library to use for our new project. We are building an auth-server in Node and need to also authenticate/authorize with LDAP-servers (Active Directory mostly). However, it's hard to pick a package that we can depend on for maintenance in the future. So hopefully the package will be transferred for maintenance
I didn’t realize it had been migrated. I never got an email or anything notifying me. Let me have some time to make sure we can publish things and get the lay of the land so to speak.
I did a little bit of work tonight merging some low hanging fruit PRs into a new next branch. It would be helpful if people could look through PRs and start some new ones to add unit tests to PRs that are likely abandoned and are missing tests.
The priority should be getting the library working on current LTS and Node 12. Then an npm @next release can be published and a deprecation notice added to the current latest asking for people to test it out.
Activity
tastypackets commentedon Aug 16, 2018
It seems pretty dormant from the time I have been watching it on github. I think it might be time for someone to fork it.
Artum commentedon Aug 27, 2018
Did you guys tried to contact the maintainer by email?
jgeurts commentedon Aug 27, 2018
That's a good idea. I haven't tried, but I'll give it a shot!
melloc commentedon Aug 27, 2018
(Sorry, misread the URL earlier, and thought this was a different ticket. Posting new comment.)
@jgeurts Sorry for the lack of activity lately. I'd planned on taking care of them earlier this year when I transferred the repo, but I've had other things come up, and haven't had the time to fix things correctly. I'm hoping to work my way through them soon. Is there a specific ticket you were looking at?
jgeurts commentedon Aug 27, 2018
No worries, I definitely understand how things come up, just didn't want the project to become abandoned. I'm mainly interested in #485. That is preventing us from updating to node v10.
purplemana commentedon Oct 11, 2018
The pending PRs are still in wait. It'd be great to see the repo back in action.
nytsua commentedon Nov 5, 2018
@joyent Are you looking for people to help with PRs?
jvanalst commentedon Nov 5, 2018
I'm with @jgeurts. As soon as #485 is fixed we're in business again. I think that should be the first priority.
jgeurts commentedon Nov 5, 2018
I'm not convinced this project is active anymore, unfortunately.
If anyone is interested, I have started working on the https://github.com/ldapts/ldapts project. The goal, aside from adding type information, is to modernize the syntax a bit and fix some outstanding issues.
It's still very early in development (I'm working on Client first) and I welcome anyone who wants to lend a hand...
tastypackets commentedon Nov 6, 2018
@jgeurts I'll be watching your progress, hopefully it will turn into a maintained alternative to ldapjs.
acappella2017 commentedon Nov 22, 2018
@melloc
Node.js starts LTS for V10 since Oct. 30, can we merge #485 to support Node 10?
sunpeinju commentedon Nov 28, 2018
@melloc
Could you take a look at #497 ? Witch enables Node.js V10 support and all UTs have passed.
sunpeinju commentedon Nov 30, 2018
@joyent Could any body help to handle #497 ?
ldapjs is broken with Node.js V10 and we want to bring it back to live.
jgeurts commentedon Dec 10, 2018
If anyone needs node v10+ support, I've been using https://www.npmjs.com/package/ldapts for over a week to connect to a couple active directories with > 30k users. It has been working well and includes the fixes in #497.
hcderaad commentedon Feb 5, 2019
For those looking for a lightweight LDAP server protocol implementation, perhaps this (pure) PHP library is an option worth considering: https://github.com/FreeDSx/LDAP/blob/master/docs/Server/General-Usage.md
Besides that there is also a Go LDAP client/server implementation: glauth
But for web developers the PHP switch might be a closer call.
kspearrin commentedon Mar 22, 2019
2019 now and #485 still hasn't been fixed. Should we just move to ldapts?
rienheuver commentedon Jul 9, 2019
@melloc has responded June 22 2019 here: nodejs/package-maintenance#221
Currently at our work we are trying to make a choice for which library to use for our new project. We are building an auth-server in Node and need to also authenticate/authorize with LDAP-servers (Active Directory mostly). However, it's hard to pick a package that we can depend on for maintenance in the future. So hopefully the package will be transferred for maintenance
UziTech commentedon Aug 20, 2019
@jsumners since this repo moved to @ldapjs, are we going to see more active development?
I have an active fork at UziTech/node-ldapjs that I have been merging some of the pull requests to.
I have also been trying to update the codebase to use newer ES features and stable dependencies in https://github.com/UziTech/node-ldapjs/pull/2 available at @uzitech\ldapjs@next
I would be happy to join the team and help get ldapjs back to actively maintained.
jsumners commentedon Aug 20, 2019
I didn’t realize it had been migrated. I never got an email or anything notifying me. Let me have some time to make sure we can publish things and get the lay of the land so to speak.
melloc commentedon Aug 20, 2019
@jsumners I've created an
ldapjsorganization on npm, and invited you to it. I've added theldapjspackage to the organization'sdeveloperteam.jsumners commentedon Aug 20, 2019
@melloc 👍
I'll start looking into this stuff soon.
At some point we may want to figure out website stuff, but I'll want to focus first on some package updates.
jsumners commentedon Aug 25, 2019
I did a little bit of work tonight merging some low hanging fruit PRs into a new
nextbranch. It would be helpful if people could look through PRs and start some new ones to add unit tests to PRs that are likely abandoned and are missing tests.The priority should be getting the library working on current LTS and Node 12. Then an npm
@nextrelease can be published and a deprecation notice added to the current latest asking for people to test it out.jsumners commentedon Aug 26, 2019
I'm closing this issue because it is basically resolved. A new release will come when it is ready.
jsumners commentedon Mar 10, 2023
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.