Uploaded image for project: 'Couchbase Documentation'
  1. Couchbase Documentation
  2. DOC-7493

Correct usage of LDAP with Java SDK 3.x

    XMLWordPrintable

Details

    Description

      This is the link I would like to amend:  https://docs.couchbase.com/java-sdk/3.0/howtos/sdk-authentication.html#ldap

      If LDAP is enabled, Couchbase Server will only allow PLAIN sasl authentication which by default, for good security, the SDK will not allow.

       In SDK 3.x, only SASL SCRAM is allowed for non-TLS.  To use LDAP on a non-TLS connection, SASL PLAIN should be forced with .onlyEnablePlainSaslMechanism(). This requires 3.0.9+

      Here is an example:

      PasswordAuthenticatorauthenticator = PasswordAuthenticator 
       .builder() 
       .username("gauss") 
       .password("password")
       .onlyEnablePlainSaslMechanism()
       .build();

       

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          richard.smedley Richard Smedley added a comment - Fixed in 3.1 https://docs.couchbase.com/java-sdk/current/howtos/sdk-authentication.html#ldap (Does not apply in 3.0 for most users)

          Richard Smedley just want to follow up on the above comment quickly - is there a particular reason this won't affect users in 3.0?

          James Flather James Flather added a comment - Richard Smedley just want to follow up on the above comment quickly - is there a particular reason this won't affect users in 3.0?

          Before 3.0.9, the SDK did not enforce PLAIN with TLS, JVMCBC-890,
          most 3.0 doc readers will be there because stuck for now on an earlier version,
          and most readers will end up on current (3.1) docs....
          given current limited bandwidth, this seemed to catch most caser.

          richard.smedley Richard Smedley added a comment - Before 3.0.9, the SDK did not enforce PLAIN with TLS, JVMCBC-890 , most 3.0 doc readers will be there because stuck for now on an earlier version, and most readers will end up on current (3.1) docs.... given current limited bandwidth, this seemed to catch most caser.

          People

            richard.smedley Richard Smedley
            hitesh.walia Hitesh Walia
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty