Skip to content
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

hotfix(cassandra) auth for C* providers and C* timeout configuration #937

Merged
merged 2 commits into from
Feb 3, 2016

Conversation

thibaultcha
Copy link
Member

No description provided.

lua-cassandra 0.5.0 allows to use plain text auth provider arbitrarily,
which re-enables authentication capabilities with C* providers from
Kong.

Background:
< 0.5.0 relied on the Java class name returned in the auth challenge
response to select the appropriate authentication provider. But C*
providers such as Instaclustr implemented their own Java authentication
provider, which must also be answered by the plain text auth provider.
0.5.0 would not recognize custom Java class as valdi authentication
providers and thus, fail to authenticate. 0.6.0 allows to set any auth
provider the user want. In our case, if Kong has username and password
configured, we always use a plain text auth provider.
@thibaultcha thibaultcha force-pushed the hotfix/cassandra-auth branch 2 times, most recently from 67d8eb2 to fa39b65 Compare February 3, 2016 10:52
@thibaultcha thibaultcha force-pushed the hotfix/cassandra-auth branch from fa39b65 to d9fbe01 Compare February 3, 2016 20:17
@thibaultcha thibaultcha added the pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release) label Feb 3, 2016
thibaultcha added a commit that referenced this pull request Feb 3, 2016
hotfix(cassandra) auth for C* providers and C* timeout configuration
@thibaultcha thibaultcha merged commit 590122b into master Feb 3, 2016
@thibaultcha thibaultcha deleted the hotfix/cassandra-auth branch February 3, 2016 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant