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

ASF GitHub Bot updated FLINK-39006:
-----------------------------------
    Labels: documentation pull-request-available  (was: documentation)

> Flink Document correction
> -------------------------
>
>                 Key: FLINK-39006
>                 URL: https://issues.apache.org/jira/browse/FLINK-39006
>             Project: Flink
>          Issue Type: Bug
>            Reporter: lajith
>            Priority: Major
>              Labels: documentation, pull-request-available
>
> For configuring SSL enabled for internal and external connectivity, as per 
> Flink 1.20 doc it has been mentioned that 
> _Note: For backwards compatibility, the *security.ssl.enabled* option still 
> exists and enables SSL for both internal and REST endpoints_
>  
> _link : 
> [https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/deployment/security/security-ssl/#:~:text=Note%3A%20For%20backwards%20compatibility%2C%20the%20security.ssl.enabled%20option%20still%20exists%20and%20enables%20SSL%20for%20both%20internal%20and%20REST%20endpoints.]_
> Which looks fine as per the code here 
> [https://github.com/apache/flink/blob/release-1.20.3/flink-core/src/main/java/org/apache/flink/configuration/SecurityOptions.java#L684]
>  , as _*security.ssl.enabled*_ was _**_ deprecated in Flink 1.20 and there 
> was a fallback option provided.
>  
> But in Flink 2.x ,  _*security.ssl.enabled*_  config  is removed 
> [https://github.com/apache/flink/blob/release-2.2.0/flink-core/src/main/java/org/apache/flink/configuration/SecurityOptions.java#L629.]
>  
>  
> But still flink 2.x doc says 
>  
> _Note: For backwards compatibility, the *security.ssl.enabled* option still 
> exists and enables SSL for both internal and REST endpoints._
> _link : 
> [https://nightlies.apache.org/flink/flink-docs-release-2.1/docs/deployment/security/security-ssl/#:~:text=Note%3A%20For%20backwards%20compatibility%2C%20the%20security.ssl.enabled%20option%20still%20exists%20and%20enables%20SSL%20for%20both%20internal%20and%20REST%20endpoints.]_
>  
> which is misleading __ and doc should be updated{_}.{_} 
>  



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

Reply via email to