TAP - Should the bucket be secured(SASL)?
Tue, 08/30/2011 - 09:32
The configuration I have:
A non SASL membase bucket "testbucket" hosted in port 11212
The default bucket on 11211 is deleted
No other buckets exist on the cluster
I am failing to tap the bucket hosted on 11212 using the python example client as below; not sure if this is possible at all for a non-SASL bucket?
The membase "console" user and password are replaced in the below line:
./tap_example.py -u user -p pass ip:11210
Error:
mc_bin_client.MemcachedError: Memcached error #32: Auth failure
Logically this appear to make sense, since I am neither indicating the bucket name - "testbucket" nor the port (11212).
Did I miss something? Appreciate your help
Yes, this should still be possible. "Technically" all buckets are SASL accessible when talking to 11210...that's the only way to specify which bucket you're referring to.
However, a non-SASL bucket (via the config) just has a username (the bucket name) and no password. So, can you try:
./tap_example.py -u user -p "" ip:11210
Perry
Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Couchbase: http://www.couchbase.com/products-and-services/overview
Call or email "sales -at- couchbase-dot- com" today!