[
https://issues.apache.org/jira/browse/CASSANDRA-18544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17726275#comment-17726275
]
Brandon Williams commented on CASSANDRA-18544:
----------------------------------------------
+1
> 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
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 5.x
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
