-
Notifications
You must be signed in to change notification settings - Fork 20
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
Allow other password authenticator to work #100
Comments
We've hit this problem trying to migrate from DSE to Astra. For Astra it needs to support the "org.apache.cassandra.auth.AstraAuthenticator" authenticator. This seems to be compatible with "org.apache.cassandra.auth.PasswordAuthenticator" which is already supported. |
the PR hasn't been merged yet but the fix is available in docker image |
Co-authored-by: Lukasz Antoniak <[email protected]>
The current code only accepts
com.datastax.bdp.cassandra.auth.DseAuthenticator
andorg.apache.cassandra.auth.PasswordAuthenticator
, which unnecessarily limits the kind of CQL data stores that can be used asOrigin
orTarget
. The proposed change takes the same approach that CQL python driver takes, i.e. if it's not a DSEAuthenticator, it will assume the CQL data store uses a compatible password authenticator. When we need to handle more non-password authenticators, this segment will likely change back to switch statement, but that's going to be a bigger change any way.┆Issue is synchronized with this Jira Task by Unito
┆Components: Proxy
┆Issue Number: ZDM-530
The text was updated successfully, but these errors were encountered: