LDAP integration improvements

[jonsbun]

Is your feature request related to a problem? Please describe.
CloudBeaver 24.1.0 finally got LDAP support. However, according feedback LDAP integration lack of main functionally to use it properly at this moment.

Describe the solution you'd like

1. Missing configuration of the bind user (service account) to the LDAP server.
   In general, an LDAP query looks something like this: ldapsearch -x -D "<bind-user>" -w "<bind-password>" -b "<base-dn>" "<filter>" -H "<ldap-host>:<ldap-port>". From the current configuration looks like the bind user is not used at all.

2. Missing configuration of the unique identifier for the user.
   Depending on the LDAP this attribute could be uid, sAMAccountName, mail, etc. At this moment no clue what is being used in CloudBeaver LDAP authentication.

3. Impossible to map LDAP users with the CloudBeaver Teams.

[EvgeniaBzzz]

@jonsbun
Thank you for summarizing all the feedback!
We will make improvements in future releases.

[brunobergamo]

HI, The ldap that I have to connect, it is not necessary to set the userName with cn=.

In LdapAuthProvider, we have :

        String cn = "cn=" + userName;
        var principal = Stream.of(cn, unit, ldapSettings.getBaseDN())
            .filter(CommonUtils::isNotEmpty)
            .collect(Collectors.joining(","));
        environment.put(Context.SECURITY_PRINCIPAL, principal );

I do need to set Context.SECURITY_PRINCIPAL with my userName with @Domain .
environment.put(Context.SECURITY_PRINCIPAL, userName );

Is this open issue handle this case ?

Best Regards

[EvgeniaBzzz]

In version 24.2.0 the first two points have been implemented.

New parameters added:
ldap-cn - User identifier attribute
ldap-bind-user - Bind User DN
ldap-bind-user-pwd - Bind User Password
ldap-filter - User Filter

Some extra information you can find in the LDAP Authentication article