Couchbase Ruby client library

http auth is not asserted correctly with bucketname only, should default to bucketname even if no username is supplied

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1.1
  • Fix Version/s: 1.2.0.dp6
  • Component/s: None
  • Security Level: Public
  • Labels:
    None

Description

User tried to use just :bucket_name and :bucket_password, in which case HTTP basic auth should be asserted, but that didn't happen.

See http://stackoverflow.com/questions/11319166/adding-a-new-couchbase-bucket-caused-bucketnotfound-error

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Sergey Avseyev added a comment -
Ok, I can accept the bug and show deprecation warnings if someone will use :bucket_password and :bucket_name
Show
Sergey Avseyev added a comment - Ok, I can accept the bug and show deprecation warnings if someone will use :bucket_password and :bucket_name
Hide
Permalink
Sergey Avseyev added a comment -
http://review.couchbase.org/18934

Now the client will use bucket name as username, but silently eat all other options. There is another ticket about claiming allowed options RCBC-65
Show
Sergey Avseyev added a comment - http://review.couchbase.org/18934 Now the client will use bucket name as username, but silently eat all other options. There is another ticket about claiming allowed options RCBC-65

People

  • Assignee:
    Sergey Avseyev
    Reporter:
    Matt Ingenthron
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: