For now we stick with secure ldap connections, the ones like ldaps://server:636/
But in some cases [windows servers cough, cough, cough] it may be a PITA ti setup a LDAP secure connection, so we may have the need to enable secure or insecure connections.
In the list of AD servers the users input the full URI (ldaps://server.domain:636 or ldap://server.domain:389)
A dictionary list, prevents some typos ({secureldap: yes , urildap: server.domain, portldap: 636}) and the template builds the list from those values
Set a boolean variable as a flag to use secure or insecure for all ADs servers defined.
This last one IMHO is the worst one, as it left the user with just one option for all servers. A company can have some sambas and windows servers (a mix of secure and non-secure servers).
For now we stick with secure ldap connections, the ones like
ldaps://server:636/
But in some cases [windows servers cough, cough, cough] it may be a PITA ti setup a LDAP secure connection, so we may have the need to enable secure or insecure connections.