[
https://issues.apache.org/jira/browse/KUDU-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-2013:
--------------------------------
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.
was:
>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.
Component/s: client
> Long lived auth tokens in Java client
> -------------------------------------
>
> Key: KUDU-2013
> URL: https://issues.apache.org/jira/browse/KUDU-2013
> Project: Kudu
> Issue Type: Task
> Components: client, java, security
> Affects Versions: 1.3.0
> Reporter: Mike Percy
> Assignee: Alexey Serbin
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
