Invalid Password after upgrading to CB v4.6

Couchbase Server
,
1

After upgrading to coucbhase 4.6 from 4.5.0 I have started receiving the following InvalidPasswordException. I’ve never had bucket passwords before only password to login to couchbase Admin console. The admin console credentials are the same as what i used in 4.5 although i dont think they were never used before. is this something new in 4.6? this is for local development so i would rather not have a password on buckets if possible. Using java client 2.2.1

com.couchbase.client.java.error.InvalidPasswordException: Passwords for bucket “myBucketName” do not match.
at com.couchbase.client.java.CouchbaseAsyncCluster$1.call(CouchbaseAsyncCluster.java:210) ~[java-client-2.2.1.jar:na]
at com.couchbase.client.java.CouchbaseAsyncCluster$1.call(CouchbaseAsyncCluster.java:200) ~[java-client-2.2.1.jar:na]
at rx.internal.operators.OperatorOnErrorResumeNextViaFunction$4.onError(OperatorOnErrorResumeNextViaFunction.java:140) ~[rxjava-1.2.4.jar:1.2.4]
at rx.internal.operators.OnSubscribeMap$MapSubscriber.onError(OnSubscribeMap.java:88) ~[rxjava-1.2.4.jar:1.2.4]
at rx.observers.Subscribers$5.onError(Subscribers.java:230) ~[rxjava-1.2.4.jar:1.2.4]
at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.checkTerminated(OperatorObserveOn.java:273) ~[rxjava-1.2.4.jar:1.2.4]
at rx.internal.operators.OperatorObserveOn$ObserveOnSubscriber.call(OperatorObserveOn.java:216) ~[rxjava-1.2.4.jar:1.2.4]
at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55) ~[rxjava-1.2.4.jar:1.2.4]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_91]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_91]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_91]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_91]

2

User error. After killing my database I didn’t recreate the needed buckets. Wouldn’t have been helpful to have a more accurate exception which conveys the Bucket doesn’t exist.

3

Glad you’ve resolved it @mlblount45.

Regarding conveying that the bucket doesn’t exist, you’ll be glad to know we have some enhancements already being implemented to address this. I had originally proposed some improved error handling and between @trond and @mnunberg, we’ve expanded that into improved error handling in a number of situations. It’s still in development, but some details are in sdk-rfc 13.

In the future, this will be much more obvious since we’ll separate authentication from resource access. It’s somewhat necessarily vague at the moment, as from a security perspective the cluster doesn’t give the client info about why something failed, just that it did fail. If it gave info that a bucket existed, an attacker can then probe further to try to access the bucket.

1 Like
4

sounds good thanks @ingenthr