[ 
https://issues.apache.org/jira/browse/CASSANDRA-16456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526259#comment-17526259
 ] 

Stefan Miklosovic commented on CASSANDRA-16456:
-----------------------------------------------

point 3) with the addition that it should warn you that stuff should be in 
credentials instead of cqlshrc when it comes to username / password. We do not 
have any control over any other possible further credentials located in cqlshrc 
but username and password as these two are the most known.

point 4) same, we should emit warning as it is done now that this stuff should 
be located in credentials

The reason for the warning is that then we will remove the support of 
authentication section in cqlshrc in the next release and everything will go to 
credentials only (or as flags on the command line).

point 5) if you meant override as in "applied on top of them" then yes, you are 
basically adding one set (as a mathematical construct) to the other one with a 
detail thatit will replace values in cqlshrc by these which are as values for 
the same key in credentials file

point 6) yes, that username flag on the console, then you ask for password. 
Because out of the box you can login just without anything and it will assume 
you are loging anonymously.

> 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 50m
>  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.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to