NethServer 8 accept remote AD credentials also as bind dn, but if bind dn is used, FreePBX isn't able to use it.
This because automatically add @domain to username and prepend "@" to account_suffix.
this proposed fix to FreePBX accept als the bind dn format
An alternative solution is to query the ad using bind dn into the configure action to obtain the username in username@domain format.
Workaround is to use username@domain format when connecting NS8 to an external active directory
[waiting for upstream]
NethServer 8 accept remote AD credentials also as bind dn, but if bind dn is used, FreePBX isn't able to use it. This because automatically add @domain to username and prepend "@" to account_suffix.
this proposed fix to FreePBX accept als the bind dn format
An alternative solution is to query the ad using bind dn into the configure action to obtain the username in username@domain format.
Workaround is to use username@domain format when connecting NS8 to an external active directory