Vesa Poikajärvi

The strategy does not provide such info as this is more of a configuration error. It is sort of expected that admin credentials are provided correctly. You can pass a...

Should support as the underlaying library has the support vesse/node-ldapauth-fork#70 The implementation apparently does have a security problem vesse/node-ldapauth-fork#94 if TLS fails which would be nice to get fixed.

The reason for recreating the LdapAuth instance was originally (years ago) because after some time of not using the connection it got disconnected and there was no option to reconnect...

Oh v2 has been released, it was so long in next that I forgot the whole thing. I'll try to remember to bump the deps tomorrow

Yes, expected in a sense that it is not implemented. The underlying `ldapjs` library handles all LDAP related things really, and it does not follow referrals automatically. Quick search revealed...

I'd guess this is because the clients are bound once and reused on subsequent calls, and then the connection becomes stale for some reason. There are not even an error...

@jrajav Cool. Yeah, just what I meant - attach listeners to clients in `LdapAuth` for the events emitted from that linked file (I didn't quickly find documentation for the events,...

@Kahn thanks for detailed how-to-reproduce instructions, I'll look into this. I take it from your description that `ldapjs` does reconnect as expected. Having not yet tried this I believe this...

It might be incorrect, yes, as I find writing those typedefs a bit cumbersome. I did follow examples of existing typedefs and can use it like I intended: ```typescript import...

Sorry I've been really lazy with this whole project. But this is something I cannot verify to work but you have tried this in real life use? The code looks...