I figured out that prtg uses an unencrypted ldap connection to my domain controller. The Domain Controller supports LDAPS. Other tools already connecting via ldaps on port 636 to this domain controler. What do I have to do to configure prtg to use ssl?
How can I force PRTG to use LDAPS (port 636) for Active Directory Integration?
We're currently checking the usage of LDAPS for the Active Directory Authentication, please bear with us.
Stephan Linke, Tech Support Team
Any Updates on this? is the LDAP communication signed? otherwise it will soon stop working since unsigned/unencrypted LDAP communication will stop working soon: https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV190023
We're aware of it, and we'll do something about it. Note that the "release date" has been pushed to 03/2020, which gives us some more time :)
Any news regarding when this is planned to be released?
We hope to make it in time with the Microsoft release :)
Is there any update ?
No, not yet - as mentioned, we're currently evaluating this and hope to implement it in time. Thanks for your patience on the matter!
Hey Stephan and PRTG Team - will this thread be our best source of information on this? Or should we look for an announcement on the newsletter when this is addressed?
For your awareness, this "fix" is a requirement for us, and could make PRTG a non-usable product for us if not addressed.
With some first tests, it shows that PRTG will continue to work, but the LDAP Sensor stops working.
Do you mean we can authenticate to PRTG through LDAPS successfully, per your testing? That would be great news.
I am really concerned with this issue. Yesterday I performed a test on my domain enabling LDAPS and many things stopped working.
What things in particular, if I may ask?