Re: Authentication in cassandra binary protocol v2

2013-10-29 Thread Sylvain Lebresne
Only AUTH_SUCCESS will be sent on correct authentication. The fact READY mention CREDENTIALS is indeed a left-over of the v1 doc. I'll fix the spec ant try to clarify this a bit somehow. -- Sylvain On Mon, Oct 28, 2013 at 8:06 PM, Mathieu D'Amours wrote: > I think figured it out wrong initially

Re: Authentication in cassandra binary protocol v2

2013-10-28 Thread Mathieu D'Amours
I think figured it out wrong initially. I thought AUTH_CHALLENGE was the message the server sends right after STARTUP. If I understand correctly a server configured with the PasswordAuthenticator is going to expect this flow: C -> [STARTUP] S -> [AUTHENTICATE] "PasswordAuthenticator" C -> [AUTH_R

Re: Authentication in cassandra binary protocol v2

2013-10-28 Thread Sylvain Lebresne
What information are you looking for? As the comment says, the details are authenticaticator specific. So you were right to look into PasswordAuthenticator in particular, and to be more precise you'll want to look at PasswordAuthenticator.PlainTextSaslAuthenticator.evaluateResponse() for that that

Authentication in cassandra binary protocol v2

2013-10-28 Thread Mathieu D'Amours
Hello, I stumbled upon this description in the binary protocol specs [4.2.7. AUTH_CHALLENGE]: > The body of this message is a single [bytes] token. The details of what this > token contains (and when it can be null/empty, if ever) depends on the actual > authenticator used. I looked in C* buil