-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manager should not assume CQL-SSL in cluster sessions #3679
Milestone
Comments
I think, in the end, whether to use TLS or not should be a per cluster option, the same as the TLS certs. That said, at least a global option would be a good start. |
This was referenced Jan 11, 2024
vponomaryov
added a commit
to vponomaryov/scylla-cluster-tests
that referenced
this issue
Jan 19, 2024
Starting with the 'v1.11.0' version of the scylla-operator the TLS feature gets enabled by default. At first, we do not need it. At second, it makes the scylla-manager operations fail [1]. So, disable it explicitly if we do not expect it to overwrite the default setting. [1] scylladb/scylla-manager#3679
2 tasks
vponomaryov
added a commit
to vponomaryov/scylla-cluster-tests
that referenced
this issue
Jan 19, 2024
Starting with the 'v1.11.0' version of the scylla-operator the TLS feature gets enabled by default. At first, we do not need it. At second, it makes the scylla-manager operations fail [1]. So, disable it explicitly if we do not expect it to overwrite the default setting. [1] scylladb/scylla-manager#3679
fruch
pushed a commit
to scylladb/scylla-cluster-tests
that referenced
this issue
Jan 21, 2024
Starting with the 'v1.11.0' version of the scylla-operator the TLS feature gets enabled by default. At first, we do not need it. At second, it makes the scylla-manager operations fail [1]. So, disable it explicitly if we do not expect it to overwrite the default setting. [1] scylladb/scylla-manager#3679
karol-kokoszka
added a commit
that referenced
this issue
Feb 8, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 9, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 12, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 13, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 13, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 13, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 13, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 14, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 14, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 14, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 22, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 22, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 22, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 22, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 22, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 26, 2024
…on from DB This addresses #3679 .
karol-kokoszka
added a commit
that referenced
this issue
Feb 26, 2024
…on from DB This addresses #3679 .
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Currently, if you set up CQL-SSL in your ScyllaDB cluster, the manager sets up a TLS client when establishing a CQL session with a cluster, even if it wasn't provided with certs.
What did you expect to happen?
Scylla Manager should not use TLS by default. Scylla Manager should configure a TLS client when establishing a CQL session with a cluster only when specifically configured to do so.
How can we reproduce it?
Similarly,
sctool status
fails on fetching the TLS config.Scylla Manager version
3.2.5
Further details
Looking into the manager code, it seems that, when selecting a CQL port, it chooses between an SSL and non-SSL ports based on client encryption being enabled:
scylla-manager/pkg/scyllaclient/client_agent.go
Line 76 in 47a93b9
I think this is not correct and it should be configurable. As in the above example, you can configure both cql-ssl and cql ports, and the manager shouldn't just assume which one to use.
cc @Michal-Leszczynski @karol-kokoszka
The text was updated successfully, but these errors were encountered: