Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
Couchbase Server 5.0
-
DOC-S6-Dec29, DOC-S7-Jan12, DOC-S8-Jan26, DOC-S9-Feb09
Description
The following behaviour needs to be documented for the client SDK versions which do not have inbuilt support for RBAC in Couchbase Server 5.0:
Case 1:
Upgrade to Couchbase Server 5.0 with passwordless buckets setup in an older version of Couchabse Server:
If a cluster, having passwordless buckets, is upgraded to Couchbase Server 5.0, the corresponding RBAC user entries are generated with username equal to the bucket name and with role set to "Full Bucket Access".
The purpose of creating such user entries is to enable older SDK versions to access the buckets without creating the "Authentication Object".
The following snippet from a Java SDK with version < 2.4.4 will successfully return the bucket object as there is user which has the username "beer-sample" (same as the bucket name)
Cluster cluster = CouchbaseCluster.create(<hostname>);
|
Bucket bucket = cluster.openBucket("beer-sample");
|
Case 2:
Connecting to buckets created in Couchbase Server 5.0 itself using older Client Verisons:
To connect to buckets created in Couchbase Server 5.0 itself, using older client versions, one needs to manually create a user with username equal the bucket name with role set to "Bucket Full Access". The client can then connect to the bucket using the following sample snippet:
Cluster cluster = CouchbaseCluster.create(<hostname>);
|
Bucket bucket = cluster.openBucket(<bucket-name>, <password for the newly created user>);
|