You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "miklosovic (Jira)" <ji...@apache.org> on 2023/05/23 14:45:00 UTC

[jira] [Updated] (CASSANDRA-18544) Make cassandra-stress possible to authenticate against JMX with username and password

     [ https://issues.apache.org/jira/browse/CASSANDRA-18544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

miklosovic updated CASSANDRA-18544:
-----------------------------------
    Attachment: signature.asc

I am fine with leaving it as it is and read it from one file if specified.

What should have the priority if both are provided? I would say command line parameter would beat the file.


Sent from ProtonMail mobile



\

> Make cassandra-stress possible to authenticate against JMX with username and password
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18544
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18544
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tool/stress
>            Reporter: Stefan Miklosovic
>            Priority: Normal
>         Attachments: signature.asc
>
>
> If there is username/password required in order to connect via JMX, there is currently no way how to do this as NodeProbe constructor in cassandra-stress does not accept any credentials. 
> The way how we are reading the credentials should be refactored. Currently, if there are credentials on the command line, they will be visible in the logs. Making it visible on the command line for JMX credentials is not ideal either.
> What I would like to see is to read all credentials which are necessary for cassandra-stress from ONE file. CQL and JMX combined. 
> Because there is already some logic in place and it would be cool to have this backward compatible, we may still support command line credentials for CQL but we would make it deprecated and we would remove it in 6.0 so cassandra-stress will be reading credentials from the file only.
> I looked into the implementation and I have an idea how to "inject" credentials where necessary so they would be used even we do not use them on the command line but I have not coded up anything yet.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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