[GH-ISSUE #2715] LDAP integration improvements #903

New issue

Open

opened 2026-03-07 20:56:28 +03:00 by kerem · 0 comments

kerem commented

2026-03-07 20:56:28 +03:00

Owner

Originally created by @jonsbun on GitHub (Jun 17, 2024).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/2715

Originally assigned to: @HocKu7 on GitHub.

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

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.
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.
Impossible to map LDAP users with the CloudBeaver Teams.

Originally created by @jonsbun on GitHub (Jun 17, 2024). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/2715 Originally assigned to: @HocKu7 on GitHub. **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.

Rows
Columns