Details
Description
Our Native LDAP client doesn't support certificate authentication to the LDAP server.
Old saslauthd, even though was much inferior in many things, does support it via it's settings
ldap_tls_cert: cert.crt
ldap_tls_key: pkey.key
It is important for cases client would like to authenticate with remote LDAP like google GCP.
Currently we support LDAP communication unsecured, secured with Certificate validation or without. However every one of these method require username and password.
Attachments
Issue Links
- is cloned by
-
MB-40713 Native LDAP client should support certificate authentication
-
- Closed
-
- is triggering
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
MB-37802 UI: Certificate field in LDAP configuration dialog is confusing
-
- Closed
-
- mentioned in
-
Page Loading...
| For Gerrit Dashboard: MB-37718 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 121999,1 | MB-37718: LDAP client cert authentication | master | ns_server | Status: ABANDONED | 0 | 0 |
| 122001,5 | MB-37718: LDAP client cert authentication | mad-hatter | ns_server | Status: MERGED | +2 | +1 |
| 126047,2 | Merge remote-tracking branch 'couchbase/mad-hatter' | master | ns_server | Status: MERGED | +2 | +1 |
| 127880,10 | MB-37718: add Client Cert fields to LDAP Config dialog | mad-hatter | ns_server | Status: MERGED | +2 | +1 |
| 128376,1 | Merge remote-tracking branch 'couchbase/mad-hatter' | master | ns_server | Status: MERGED | +2 | +1 |
| 128452,2 | MB-37718: pass empty string if cert is not selected | mad-hatter | ns_server | Status: MERGED | +2 | +1 |
| 128457,2 | Merge remote-tracking branch 'couchbase/mad-hatter' | master | ns_server | Status: MERGED | +2 | +1 |