[bitnami/cassandra] Cannot login to cassandra using cqlsh (Authentication Issue) about charts HOT 9 CLOSED

nice bro @dgomezleon @javsalgar
this is good solution. is available.

from charts.

When there is a PVC, the installation will re-use the password from the volume. Could you confirm what the previous password was?

from charts.

Hi @amirhallaji

I was not able to reproduce the issue. I tried the following.

1. Install the chart with default values only using dbUser.password="cassandra"
2. Access with the following commands

   kubectl port-forward --namespace test svc/cassandra 9042:9042 &
   cqlsh -u cassandra -p cassandra 127.0.0.1 9042

4. Uninstall it and keep PVC.
5. Install again
6. Access with the previous commands.

I would suggest using these commands in case it helps:

$ export CASSANDRA_PASSWORD=$(kubectl get secret --namespace "test" cassandra -o jsonpath="{.data.cassandra-password}" | base64 -d)
$  kubectl port-forward --namespace test svc/cassandra 9042:9042 &
$  cqlsh -u cassandra -p $CASSANDRA_PASSWORD 127.0.0.1 9042

from charts.

Hi @amirhallaji

You could try the following to apply this docs:

1. Copy the original configuration:

$ kubectl cp cassandra-0:/opt/bitnami/cassandra/conf/cassandra.yaml /tmp/cassandra.yaml

2. Edit it as follows

...
# - AllowAllAuthenticator performs no checks - set it to disable authentication.
# - PasswordAuthenticator relies on username/password pairs to authenticate
#   users. It keeps usernames and hashed passwords in system_auth.roles table.
#   Please increase system_auth keyspace replication factor if you use this authenticator.
#   If using PasswordAuthenticator, CassandraRoleManager must also be used (see below)
authenticator: 'AllowAllAuthenticator'

# Authorization backend, implementing IAuthorizer; used to limit access/provide permissions
# Out of the box, Cassandra provides org.apache.cassandra.auth.{AllowAllAuthorizer,
# CassandraAuthorizer}.
#
# - AllowAllAuthorizer allows any action to any user - set it to disable authorization.
# - CassandraAuthorizer stores permissions in system_auth.role_permissions table. Please
#   increase system_auth keyspace replication factor if you use this authorizer.
authorizer: 'AllowAllAuthorizer'
...

3. Create a CM

$ kubectl create cm cassandra-conf --from-file=/tmp/cassandra.yaml

4. Uninstall the chart and install it as follows

helm install cassandra . --set existingConfiguration=cassandra-conf

5. Access with cqlsh (with empty password) and set it to cassandra:

$ cqlsh -u cassandra 127.0.0.1 9042
  cqlsh> UPDATE system_auth.roles SET salted_hash = '$2a$10$1gMPBy9zSkDzKxdbU2v/gOslcMRPDcXVqmwQYBmi8MVgYvNdRZw/.' WHERE role = 'cassandra';
  cqlsh> exit 

6. Uninstall and install the chart as usual.

You should be able to access it with cassandra password.

from charts.

Hi dear @dgomezleon

Thank you very much. It worked for me.

from charts.

Hi!

Could you confirm if you do not have PVC leftovers from previous installations?

from charts.

Hi,
I did not delete pvc since I didn't want to lose data.
As I know, the deletion of PVC results in losing data if no backup is provided.
Should I have done something else?

from charts.

I got it.
Yes, the previous password was cassandra which I used to log in. But, after installing it again, this password didn't work anymore.

from charts.

Hi @dgomezleon

Thank you for your suggestion. Actually, I had done these steps multiple times before creating this issue, but unfortunately, they didn't work for me. I think the only solution may be to delete PVC. Am I right?

I also should mention that the first time I uninstalled the chart, it was due to the lack of resources in that namespace that made me do that. I don't know whether it's helpful or not. But I add it to this issue.

from charts.