[jira] [Commented] (SLIDER-413) token renewal scheme misinterprets expiry time from Token.renew()

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLIDER-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127710#comment-14127710 ] 

ASF subversion and git services commented on SLIDER-413:
--------------------------------------------------------

Commit ce0c05278aa4d7718e3005d756cabff747f3fc5a in incubator-slider's branch refs/heads/develop from [~jmaron]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=ce0c052 ]

SLIDER-413 fixed renewal logic to read token expiry time


> token renewal scheme misinterprets expiry time from Token.renew()
> -----------------------------------------------------------------
>
>                 Key: SLIDER-413
>                 URL: https://issues.apache.org/jira/browse/SLIDER-413
>             Project: Slider
>          Issue Type: Bug
>          Components: security
>            Reporter: Jonathan Maron
>            Assignee: Jonathan Maron
>
> The current HDFS delegation token renewal framework invokes Token.renew() and assumes the expiry time returned is the expiry time for the token.  Further investigation appears to show that it is in fact the time at which the token should next be renewed, rather than the max time for the token.  Given that, the current scheme may not be optimal since it will probably trigger the retrieval of new tokens much more often than necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)