-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UnsupportedOperationException: SASL is not supported for ASCII protocol #6
Comments
SASL is only supported by Memcached's binary protocol:
There is no way to add SASL into text protocol in a backwards-compatible way. |
I don't have access to the server. I'm just connecting to it with a username and password, using |
It should use binary protocol. I can't immediately say what may cause text protocol to be used, Spyglass uses Spymemcached's binary connection factory which should set everything up for us. |
I have a theory about what may be going but don't have a SASL-enabled memcached instance to test against. Can you email me credentials I can use? It will only be necessary for a couple of days. |
Please try |
I'll check it out. Just sent you an email if you want to test it yourself. |
Looks like this particular exception is gone but I cannot yet get the test suite to pass using binary protocol with SASL. |
Debugging a local copy of Memcached built with SASL and plain text password DB support suggests binary connections now work fine, however, authentication still fails. |
Got the below, is I call select all after delete a id 2013-08-14 23:54:05.257 WARN net.spy.memcached.transcoders.SerializingTranscoder: Caught CNFE decoding 2768 bytes of data |
has nothing to do with Spyglass or Memcached. Also, if you have an issue, file a new one or ask on the mailing list instead of leaving comments to existing ones. |
Fixes issue clojurewerkz#6. + Fix SASL authentication errors for Heroku users. + Allow passing an optional auth-type argument to spyglass.client/bin-connection. + Pull out net.spy.memcached.auth.AuthDescriptor construction to spyglass.client/auth-descriptor function. Passing :plain or :cram-md5 keywords specifies an auth mechanism. (AuthDescriptors initialized with AuthDescriptor/typical threw authentication errors for users connecting to Heroku's default memcached servers).
Was this ever resolved? I'm getting:
... on Heroku using Memcached Cloud. |
@kendagriff not to my knowledge. In addition we found out that older SpyMemcached versions don't have this issue. Testing Memcached with authentication locally has been a major pain for us. Feel free to investigate it. |
Excellent, Michael. That led to at least a workable answer. In case anyone else needs it, I set up http://blog.clojurewerkz.org/blog/2013/08/22/spyglass-1-dot-1-0-is-released/ |
Cheers to everyone at Clojurewerkz! Developing a web app with Monger and Spyglass was an absolute joy, and I'm glad you're out there abstracting ConnectionFactoryBuilders for people like me.
I'm still running into an SASL error connecting a Heroku app to a remote Memcached server. The client still seems to be using the ASCII protocol, even when I use
clojurewerkz.spyglass.client/bin-connection
. I saw that there was an authentication fix in the latest beta, so I grabbed the new code and replacedbin-connection
and all its dependencies in my project, but it throws the same exception:java.lang.UnsupportedOperationException: SASL is not supported for ASCII protocol
.I solved this issue by using the example in this blog post to set up my client and pass it to spyglass, but I'm not a Java dev and have no idea what I'm doing when I have to deal with interop stuff.
Here's my code:
And here's the whole error (server address redacted):
The text was updated successfully, but these errors were encountered: