[KUDU-2013] Long lived auth tokens in Java client

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.5.0
• Component/s: client, java, security
• Code Review: https://gerrit.cloudera.org/#/c/7250/
• Assignee: Alexey Serbin
• Reporter: Mike Percy
• Created: 15/May/17 21:47
• Updated: 12/Jul/17 21:51
• Resolved: 12/Jul/17 21:51

Description

From security.adoc:

Kudu clients do not automatically request fresh tokens after initial token expiration, so long-lived clients in secure clusters are not supported.

A process to refresh tokens about to expire would enable the use of long-lived clients with secure clusters.

NOTE: It's possible to get a new token only when primary user credentials are available. In case if a client is created using imported authenticaion_credentials (i.e. using AsyncKuduClient.importAuthenticationCredentials()), re-acquiring a new token is not possible by design.

Issue Links

• blocks: KUDU-2012 Kudu Flume sink authn support
• relates to: KUDU-2018 Kudu C++ client: re-acquire a new authn token when current one expires