[ 
https://issues.apache.org/jira/browse/FLINK-28520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-28520:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> RestClient doesn't use SNI TLS extension
> ----------------------------------------
>
>                 Key: FLINK-28520
>                 URL: https://issues.apache.org/jira/browse/FLINK-28520
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / REST
>    Affects Versions: 1.13.6, 1.14.5, 1.15.1
>            Reporter: Jean-Damien HATZENBUHLER
>            Assignee: Jean-Damien HATZENBUHLER
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>
> The {{org.apache.flink.runtime.rest.RestClient}} didn't use SNI TLS extension 
> when ssl options are activated.
>  
> This cause the {{flink cli}} not be able to communicate with 
> {{{}jobmanager{}}}.
> h2. How to fix this issue:
> Use:
> {code:java}
> public SslHandler createNettySSLHandler(ByteBufAllocator allocator, String 
> hostname, int port)
> {code}
> instead of 
> {code:java}
> public SslHandler createNettySSLHandler(ByteBufAllocator allocator)
> {code}
> h2. How to reproduce this issue:
> Given:
> * An existing {{flink}} instance running without ssl options
> * An existing certificate for the _hostname_
> * An existing load balancer with SNI like {{traefik}} and without a default 
> certificate between the existing {{flink}} instance and the  {{flink cli}}
> * A {{flink cli}} configured with the ssl options
> When:
> * Run the command {{flink list --jobmanager _hostname_:443}}
> Then:
> * You will get an error {{unrecognized_name}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to