File Server configuration requires exact case matching for external AD domain

[nrauso]

If you want to configure the file server app using an external Active Directory (AD) account provider, you must specify the external account provider with the correct case in the Domain field.
If the case in the Domain field is incorrect, the file Server’s join to the external account provider will fail.

Steps to Reproduce

• Install NS8.
• Add an external AD account provider to the node, entering the AD domain in uppercase in the Domain field.
• Install the File Server app and attempt to join it to the external AD account provider.

Expected Behavior

The operation should complete successfully.

Actual Behavior

The join fails, and the configure-module task shows the following error:

Active Directory domain ad.test.org: no changes needed to IP routing configuration.
<3> Address resolution error: name 'peer_address' is not defined

🚨 IMPORTANT NOTE 🚨
In the documentation, we recommend using global catalog ports (3268/TCP, 3269/TCP) to bind NS8 to an external AD account provider.
However, with this configuration, the LDAP query performed by the file server setup to discover the AD NetBIOS name fails, causing the join operation to fail as well.
To use an external AD account provider with the file server app, bind using the standard LDAP port (389/TCP) or the secure LDAPS port (636/TCP).

Components

• core:3.12.3
• samba:3.1.1

[DavidePrincipi]

In Testing samba 3.2.0-dev.4

Test case 1

1. Check the bug is not reproducible with stable with a remote Microsoft AD provider with port 389
2. Update to Testing
3. No regressions

Test case 2

1. Check the bug is reproducible with stable with a remote Microsoft AD provider with GC port 3268
2. Update to Testing
3. The bug has been fixed

Test case 3

1. Check the bug is not reproducible with stable with a remote Samba AD provider with port 389 or 3268
2. Update to Testing
3. No regressions

[DavidePrincipi]

Updated testing target to 3.2.0-dev.4