[
https://issues.apache.org/jira/browse/CASSANDRA-16456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521067#comment-17521067
]
Stefan Miklosovic commented on CASSANDRA-16456:
-----------------------------------------------
Just to add what [~Bowen Song] said, when you get to the implementation, I
would pass all content of credentials file (for that auth provider) into the
constructors arguments, together with all other settings for auth provider in
cqlshrc, credentials replacing possible duplicities in cqlshrc.
I am not sure if it is necessary to store credentials per auth provider in
credentials file (like there would be multiple sections and you would choose
which one to include based on what auth provider is active in cqlshrc), if you
manage to do that that would be nice but it is not required.
If I have this
{code}
cat ~/.cassandra/credentials
[plain_text_auth]
username = cassandra
password = cassandra
{code}
and this
{code}
cat ~/.cassandra/cqlshrc
[authentication]
credentials = /home/smiklosovic/.cassandra/credentials
[auth_provider]
module = cassandra.auth
classname = PlainTextAuthProvider
{code}
I am not sure how we want to map the content of credentials to that auth
provider because we need to somehow map "plain_text_auth" to
"PlainTextAuthProvider". I would hence start to do it like this:
{code}
cat ~/.cassandra/credentials
[PlainTextAuthProvider]
username = cassandra
password = cassandra
{code}
> Add Plugin Support for CQLSH
> ----------------------------
>
> Key: CASSANDRA-16456
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16456
> Project: Cassandra
> Issue Type: New Feature
> Components: Tool/cqlsh
> Reporter: Brian Houser
> Assignee: Brian Houser
> Priority: Normal
> Labels: gsoc2021, mentor
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Currently the Cassandra drivers offer a plugin authenticator architecture for
> the support of different authentication methods. This has been leveraged to
> provide support for LDAP, Kerberos, and Sigv4 authentication. Unfortunately,
> cqlsh, the included CLI tool, does not offer such support. Switching to a new
> enhanced authentication scheme thus means being cut off from using cqlsh in
> normal operation.
> We should have a means of using the same plugins and authentication providers
> as the Python Cassandra driver.
> Here's a link to an initial draft of
> [CEP|https://docs.google.com/document/d/1_G-OZCAEmDyuQuAN2wQUYUtZBEJpMkHWnkYELLhqvKc/edit?usp=sharing].
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
