[
https://issues.apache.org/jira/browse/RANGER-5747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105777#comment-18105777
]
Vyom Mani Tiwari commented on RANGER-5747:
------------------------------------------
The {{NiFiClient}} half of this fix (PR #682) did not make it into the
{{{}ranger-2.8{}}}/{{{}ranger-2.9{}}} release branches, so
{{release-ranger-2.8.0}} and {{release-ranger-2.9.0}} remain affected. Tracked
and remediated via RANGER-5747
> 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
> Time Spent: 0.5h
> 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)
