[
https://issues.apache.org/jira/browse/KUDU-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720035#comment-17720035
]
ASF subversion and git services commented on KUDU-3472:
-------------------------------------------------------
Commit ede75bc162c14cb58b2c5cceef6a7072c0d7428c in kudu's branch
refs/heads/master from Zoltan Chovan
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=ede75bc16 ]
[client] KUDU-3472 Java client API to import JWT
This patch adds one new method into AsyncKuduClient and KuduClient API
to set a JWT (JSON Web Token) to be used for authentication. The newly
introduced API matches the one introduced in the C++ Kudu client.
Change-Id: Ic43bd1219f4613e9cac11762726a5d6d2cdc764b
Reviewed-on: http://gerrit.cloudera.org:8080/19836
Tested-by: Alexey Serbin <ale...@apache.org>
Reviewed-by: Alexey Serbin <ale...@apache.org>
> Add methods to import/set JWT as a means of authentication in Kudu client API
> -----------------------------------------------------------------------------
>
> Key: KUDU-3472
> URL: https://issues.apache.org/jira/browse/KUDU-3472
> Project: Kudu
> Issue Type: Improvement
> Reporter: Alexey Serbin
> Priority: Major
>
> As of 2023-04-21 in the master branch of the git repository, Kudu allows
> clients to authenticate with servers server using [JWT|https://jwt.io/], JSON
> Web Tokens. However, a missing piece is a means to allow a Kudu client
> application to supply a JWT as its authentication credentials in an
> application-friendly way. The way [how it's done in recently added tests in
> Kudu test
> scaffolding|https://github.com/apache/kudu/blob/7747a7c0149d6e8f894ad3216c54db9f27b3d372/src/kudu/integration-tests/security-itest.cc#L693-L704]
> isn't the way to go if thinking about usable client API.
> It's necessary to add such a means for both C++ and Java Kudu client API.
> Ideally, the corresponding C++ and Java parts of the API should match and be
> very similar.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
