feat: support cert and key for LDAPS

[flegastelois]

Q	A
Bug fix?	yes and no
New feature?	yes
BC breaks?	no
Deprecations?	no
Tests pass?	yes
Fixed tickets	NA

Need 3 new column in "glpi_authldap":

ALTER TABLE `glpi_authldaps`
   ADD COLUMN `tls_certfile` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8_unicode_ci',
   ADD COLUMN `tls_keyfile` VARCHAR(255) NULL DEFAULT NULL COLLATE 'utf8_unicode_ci',
   ADD COLUMN `use_bind` TINYINT(1) NOT NULL DEFAULT '1';

These changes allow the LDAP authentication / import / directory synchronization to work with secure servers that require a certificate and a private key for connection: this explains the two added option fields (tls_certfile, tls_keyfile).

Although they are called "tls_", you must not enable TLS for the connection to work, which is why I have not conditioned their addition (ldap_set_option) to the boolean "use_tls".

Google Workspace for example:
https://support.google.com/a/answer/9190869?hl=en&ref_topic=9048334#zippy=%2Cldapsearch

LDAPTLS_CERT={crt_file} LDAPTLS_KEY={key_file} ldapsearch -H ldaps://ldap.google.com:636 -b dc={domain},dc={domain} '(mail={user_email})'

In the case of using a certificate and its private key, "ldap_bind" must not be used, this explains the added option.

I can give you production ready "certificate / key" files to add in "GLPI_CONFIG_DIR/ldap/" directory.

[flegastelois]

Should be interesting, to have a "Google Workspace" pre-configured schema (like "AD" or "Default") when we create a new ldap authentification server.

https://support.google.com/a/answer/9188164?hl=en&ref_topic=9048334

• Server: ldaps://ldap.google.com
• Port: 636
• ConnectionFilter: (objectClass=person)
• Use bind: no
• Login field: mail
• Synchronization fiel : entryuuid
• Use TLS: no