[
https://issues.apache.org/jira/browse/RANGER-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj resolved RANGER-4110.
--------------------------------------
Fix Version/s: 2.4.0
Resolution: Fixed
[~ramackri] - thank you for the fix. The patch is merged in master and
ranger-2.4 branches.
{noformat}
commit 2124ed60d572ab2663f1bcea4807902e21ffe5b2 (HEAD -> master, origin/master,
origin/HEAD)
Author: Ramachandran Krishnan <[email protected]>
Date: Fri Feb 24 11:57:19 2023 +0530
RANGER-4110: upgraded TLS version to 1.2
Signed-off-by: Madhan Neethiraj <[email protected]>
{noformat}
{noformat}
commit b872c967bdb1885760c0403841d29c614952c259 (HEAD -> ranger-2.4,
origin/ranger-2.4)
Author: Ramachandran Krishnan <[email protected]>
Date: Fri Feb 24 11:57:19 2023 +0530
RANGER-4110: upgraded TLS version to 1.2
Signed-off-by: Madhan Neethiraj <[email protected]>
(cherry picked from commit 2124ed60d572ab2663f1bcea4807902e21ffe5b2)
{noformat}
> Upgrade to TLS to version 1.2 -Part2
> ------------------------------------
>
> Key: RANGER-4110
> URL: https://issues.apache.org/jira/browse/RANGER-4110
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Ramachandran
> Assignee: Ramachandran
> Priority: Major
> Fix For: 3.0.0, 2.4.0
>
>
> As part of RANGER-3153 fix , we changed TLS to TLSv1.2
> Still, the following classes are using TLS
> RangerRESTClient
> RangerSslHelper
> BaseAuditHandler
> RemoteUnixLoginModule
> DefaultSchemaRegistryClient
> NiFiRegistryConnectionMgr
> So, we need to change the above classes as well
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
