[
https://issues.apache.org/jira/browse/HBASE-28501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang reopened HBASE-28501:
-------------------------------
When putting up 2.4.18RC0, I found that the commit for this issue on branch-2.4
removed a constructor from IA.Public class Client.java in the rest module.
https://dist.apache.org/repos/dist/dev/hbase/2.4.18RC0/api_compare_2.4.17_to_2.4.18RC0.html#Binary_Removed
Client.Client ( Cluster cluster, Configuration conf, String trustStorePath,
Optional<String> trustStorePassword, Optional<String> trustStoreType )
We should follow the deprecated cycle when we want to remove a method from a
IA.Public class, unelss there are some special reasons.
> Support non-SPNEGO authentication methods and implement session handling in
> REST java client library
> ----------------------------------------------------------------------------------------------------
>
> Key: HBASE-28501
> URL: https://issues.apache.org/jira/browse/HBASE-28501
> Project: HBase
> Issue Type: Improvement
> Components: REST
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.4.18, 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9
>
>
> The current java client only supports the SPENGO authentication method.
> This does not support the case when an application proxy like Apache Knox
> performs AAA conversion from BASIC/DIGEST to kerberos authentication.
> Add support for BASIC username/password auth the client.
> Generally, the authentication code in the client looks quite backwards, it
> seems that most of the kerberos / auth cookie code duplicates HttpClient
> functionality. AFAICT setting HttpClient up (or letting user set it up) , and
> letting it handle authentication by itself would be a better and more generic
> solution.
> -Also add support for specifying a prefix for the URL path.-
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
