[
https://issues.apache.org/jira/browse/RATIS-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
István Fajth updated RATIS-2598:
--------------------------------
Description:
In the attached nettyutils_gap.md there is a long description about the problem
(Generated-by: Claude Opus 4.8).
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.
was:
In the attached nettyutils_gap.md 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.
> TLS provider/protocol/cipher config is not applied to DataStreamServer
> ----------------------------------------------------------------------
>
> Key: RATIS-2598
> URL: https://issues.apache.org/jira/browse/RATIS-2598
> Project: Ratis
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 3.3.0
> Reporter: István Fajth
> Priority: Major
> Attachments: nettyutils_gap.md
>
>
> In the attached nettyutils_gap.md there is a long description about the
> problem (Generated-by: Claude Opus 4.8).
> 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)
