NC fails, when installed on a seperate instance which is joined to Remote-AD

[dnutan (Marc)]

STARTTLS changes might relate to Rc2 QA/testing campaign and issue #5161 / #5396.

Is this relevant to the issue?

Microsoft AD security advisory ADV190023

As you said the main concerns are around the “remote AD” accounts provider. If the “remote AD” is also NethServer there is no issue and nothing changes because the LDAP connection is already ciphered (by default). If the “remote AD” is Microsoft there could be issues for those NethServer applications that require LDAP direct access: Nextcloud, Webtop, Roundcube, SOGo, ejabberd… In the latter case the solution is simple: once the DC has been updated and configured to require LDAP over an encry…

The final step is to actually reconfigure the clients to use one of the following connection methods:

• Simple Bind LDAP using SSL / TLS (usually on port 636) or StartTLS (usually on port 389). or
• Simple Authentication and Security Layer (SASL) LDAP with digital signing requests.

Source

[MS-ADTS]: Authentication