You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2026/07/10 17:56:00 UTC
[jira] [Assigned] (RATIS-2598) TLS provider/protocol/cipher config is not applied to DataStream server/client
[ https://issues.apache.org/jira/browse/RATIS-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz-wo Sze reassigned RATIS-2598:
---------------------------------
Component/s: Netty
Assignee: István Fajth
> TLS provider/protocol/cipher config is not applied to DataStream server/client
> ------------------------------------------------------------------------------
>
> Key: RATIS-2598
> URL: https://issues.apache.org/jira/browse/RATIS-2598
> Project: Ratis
> Issue Type: Improvement
> Components: Netty, Streaming
> Affects Versions: 3.3.0
> Reporter: István Fajth
> Assignee: István Fajth
> Priority: Major
> Attachments: nettyutils_gap.md
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In the attached nettyutils_gap.md (Generated-by: Claude Opus 4.8) there is a long description about the problem.
> TLDR is that while setting up the streaming server side, the SSLContext that is configured for Netty under the streaming server miss the providers/protocols/ciphers configs even if it is part of the TLS config because the construction logic for the SSLContext in NettyUtils (used for the streaming server configuration) does not pass these parameters.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)