Native transport port and native transport port ssl configuration

Steven Lacerda
1 min readSep 23, 2021

--

Here’s the scenario that was a little non-intuitive to me:

native transport: 9042
#native transport port ssl: 9142
client_encryption_options:
enabled: true
optional: false

With the above settings, only SSL traffic will work, and only over port 9042 because SSL and non-SSL use the same 9042 port.

native transport: 9042
native transport port ssl: 9142
client_encryption_options:
enabled: true
optional: false

With the above settings, both SSL and non-SSL traffic will work. That’s a little non-intuitive because we have client encryption optional set to false. However, since we specify both a non-SSL and an SSL port, we can use both types of traffic. 9042 will accept non-SSL and 9142 will accept SSL traffic.

native transport: 9142
native transport port ssl: 9142
client_encryption_options:
enabled: true
optional: false

With the above settings, only SSL traffic will work because we’re specifying the same port for both, so only SSL traffic will be accepted.

--

--

Steven Lacerda
Steven Lacerda

Written by Steven Lacerda

Steve Lacerda is a software engineer specializing in web development. His favorite 80’s song is Let’s Put the X in Sex by Kiss.

No responses yet