LDAPS ?

[RayDeanTech]

I've noticed recently that authenticating can take a super-long time. It's pretty bad right now.

We believe our IT department has changed something; specifically, we may be required to use LDAPS moving forward. Can this module support LDAPS?

Is there a way to point to a specific domain controller if needed?

Is there a way to troubleshoot why this module is "acting slowly"?

I don't expect an answer, but if you can point me in a direction, I can continue researching.

Thank you.

[YvesR]

LDAPs works fine with this plugin, we use this in our projects, too.
Did you try set a specific DC using NTLMDefaultDomain ?

My personal experience in large domains is also, that the DNS settings leads to the wrong DC to ask.

[RayDeanTech]

@YvesR thank you....

Right now, NTLMDefaultDomain is not specified, but NTLMDomain is equal to our domain name.

I made an assumption that we would need to change something.

IT is going to turn off LDAP, and we must use LDAPS. They've provided an endpoint... example: ldap://serverpool.domain.net:123. So, my guess is port 389 will not function anymore.

[YvesR]

Our admin approved that we can use this against LDAPs without issues. So if this takes longer time, this might be a network and/or DNS problem? Check with your admins if they can trace the requests and compare with apache logs.

[JBlond]

AFAIK the port is 636 with TLS, not 389. Is that port open?