You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/05/15 21:55:09 UTC

[jira] [Assigned] (KUDU-2013) Long lived auth tokens in Java client

     [ https://issues.apache.org/jira/browse/KUDU-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon reassigned KUDU-2013:
---------------------------------

    Assignee: Alexey Serbin

Alexey's already working on this

> 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: 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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)