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

Jeff Liu commented on CASSANDRA-8711:
-------------------------------------

hi [~mishail].
Yes. I did use the --ssl flag. Actually after I configure ~/.cassandra/cqlshrc 
file and specify ssl configuration, cqlsh will pick the ssl configuration and 
try to connect with ssl even without --ssl flag. 
However, either one worked for me in terms of connecting to cassandra.

> cassandra 2.1.2 cqlsh not able to connect when ssl client encryption enabled
> ----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8711
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8711
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jeff Liu
>             Fix For: 2.1.3
>
>
> I have been trying to setup client encryption on a three nodes 2.1.2 version 
> cassandra cluster and keep getting the following error:
> {noformat}
> Connection error: ('Unable to connect to any servers', {'localhost': 
> ConnectionShutdown('Connection <AsyncoreConnection(44536208) localhost:9160 
> (closed)> is already closed',)})
> {noformat}
> I tried with both cqlsh and datatax python cassandra-driver and no luck to 
> login.
> I created /rooot/.cassandra/cqlshrc file for cqlsh settings, the content is:
> {noformat}
> [authentication]
> username =
> password =
> [connection]
> hostname = localhost
> port = 9160
> factory = cqlshlib.ssl.ssl_transport_factory
> [ssl]
> certfile = /root/.cassandra/localhost_user1.pem
> validate = false ## Optional, true by default
> {noformat}
> my cassandra.yaml configuration related to client_encryptions:
> {noformat}
> client_encryption_options:
>     enabled: True
>     keystore: /etc/cassandra/conf/.keystore
>     keystore_password: cassnest
> {noformat}
> the keystore, truststore, cert/pem (localhost_user1.pem) key have been 
> verified to be working fine for datastax enterprise version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to