Include LDAP user domain in connection configuration

[stephdl]

Enhance the connection configuration by incorporating the LDAP user domain and improving the UI for better readability.

NethServer/dev#7103

[nethbot]

in 7.9.2009/autobuild:

• nethserver-ns8-migration-1.0.18-1.12.pr96.g0d3625a.ns7.x86_64.rpm x86_64

[nethbot]

in 7.9.2009/autobuild:

• nethserver-ns8-migration-1.0.18-1.13.pr96.gb3cd735.ns7.x86_64.rpm x86_64

[DavidePrincipi]

The ldap. prefix is not needed. Any domain name is acceptable, the only condition is that it is unique in the NS8 cluster and has at least one dot inside.

[gsanchietti]

The ldap. prefix is not needed. Any domain name is acceptable, the only condition is that it is unique in the NS8 cluster and has at least one dot inside.

While this is true, it's not the way NS8 configures the domain: it adds something leader, or ad before the domain when configuring one.
Since many users are still using bad FQDN for their machines, IMO having the ldap prefix could possible prevent some naming conflicts.

[stephdl]

in NS8, the behavior for an openldap account provider is to get the domain of the server, do not know :p

Capture.video.du.2024-12-05.15-59-33.mp4

[DavidePrincipi]

It is the same behavior of NS7.

AD prepends ad. as Microsoft recommends, it is documented in our manual. https://docs.nethserver.org/projects/ns8/en/latest/user_domains.html#dns-and-ad-domain

[stephdl]

I tested the short domain domain.com, workable, let's go to it, we could still go back if we see issue

[nethbot]

in 7.9.2009/autobuild:

• nethserver-ns8-migration-1.0.18-1.14.pr96.g489ceab.ns7.x86_64.rpm x86_64

[nethbot]

in 7.9.2009/autobuild:

• nethserver-ns8-migration-1.0.18-1.15.pr96.ga1e5fe3.ns7.x86_64.rpm x86_64