You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Vyom Mani Tiwari (Jira)" <ji...@apache.org> on 2026/09/25 03:42:00 UTC

[jira] [Resolved] (RANGER-5747) Migrate NiFiClient and NiFiRegistryClient to use RangerDefaultHostnameVerifier

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

Vyom Mani Tiwari resolved RANGER-5747.
--------------------------------------
    Fix Version/s: 3.0.0
                   2.10
                   2.9.0
       Resolution: Fixed

> Migrate NiFiClient and NiFiRegistryClient to use RangerDefaultHostnameVerifier
> ------------------------------------------------------------------------------
>
>                 Key: RANGER-5747
>                 URL: https://issues.apache.org/jira/browse/RANGER-5747
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 2.8.0, 2.9.0
>            Reporter: Vyom Mani Tiwari
>            Assignee: Vyom Mani Tiwari
>            Priority: Critical
>             Fix For: 3.0.0, 2.10, 2.9.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> RANGER-5689 introduced a shared {{RangerDefaultHostnameVerifier}} ({{{}agents-common/.../plugin/util/RangerDefaultHostnameVerifier.java{}}}), backed by Apache HttpClient's own {{{}DefaultHostnameVerifier{}}}, and migrated {{{}RangerRESTClient{}}}, {{{}RangerSslHelper{}}}, {{{}RangerAdminJersey2RESTClient{}}}, and {{RangerUgSyncRESTClient}} onto it as the single, shared implementation for TLS hostname verification across Ranger's HTTP clients.
> {{NiFiClient}} and {{NiFiRegistryClient}} were not included in that migration and still each maintain their own custom hostname-verifier implementation, independent of the shared one. This ticket proposes migrating both to {{RangerDefaultHostnameVerifier}} so that all Ranger HTTP clients share a single, consistently tested verification implementation, reducing duplicated code and the maintenance burden of keeping multiple custom verifiers in sync going forward.
> *Scope:*
>  * Replace the custom hostname-verifier inner class in {{NiFiClient.java}} with {{{}RangerDefaultHostnameVerifier{}}}.
>  * Replace the equivalent custom verifier in {{NiFiRegistryClient.java}} with {{{}RangerDefaultHostnameVerifier{}}}.
>  * Update unit test coverage in {{{}TestNiFiClient{}}}/{{{}TestNiFiRegistryClient{}}} accordingly, aligning with the existing {{TestRangerDefaultHostnameVerifier}} coverage.



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