Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-2642

ConnectionString vs Servers with TLS enabled

    XMLWordPrintable

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.7.20
    • None
    • None
    • None
    • Ubuntu 18.04 LTS
    • 1

    Description

      Background

      When we were discussing CBSE-8789,  we noted some different behavior between ConnectionString in 2.X and 3.X versions of the SDK as related to certificates when TLS is enabled. 

      Request:

      When using the 3.X code,  we were only able to get the code to connect when using localhost or enabling IgnoreRemoteCertificateNameMismatch.  However,  in 2.7.20 we encountered the scenario below.  In both cases the root certificate that is generated by Couchbase during installation was registered and used.

      Using ConnectionString with couchbases://

      When we attempt to use ConnectionString and provide it couchbases we get the following exception

      Unhandled exception. Couchbase.Configuration.Server.Serialization.BootstrapException: Could not bootstrap - check inner exceptions for details. (NodeLocator is not defined)
       ---> Couchbase.NullConfigException: NodeLocator is not defined
         at Couchbase.Configuration.ConfigContextBase.get_NodeLocator()
         at Couchbase.Core.ClusterController.CreateBucketImpl(String bucketName, String password, IAuthenticator authenticator)
         --- End of inner exception stack trace ---
         at Couchbase.Core.ClusterController.CreateBucketImpl(String bucketName, String password, IAuthenticator authenticator)
         at Couchbase.Core.ClusterController.CreateBucket(String bucketName, String password, IAuthenticator authenticator)
         at Couchbase.Cluster.OpenBucket(String bucketName, String password)
         at Couchbase.Cluster.OpenBucket(String bucketname)
         at demoapp.Program.Main(String[] args) in /home/ubuntu/demoapp2/Program.cs:line 43
      

       

      Using Servers with URI list

      However,  if we specify a URI list using https://<address>:18091,  we are able to successfully connect. 

       

      Thanks,

      Craig

      Attachments

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

        Activity

          People

            Unassigned Unassigned
            craig.kovar Craig Kovar (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty