[
https://issues.apache.org/jira/browse/HADOOP-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915420#action_12915420
]
Todd Lipcon commented on HADOOP-6656:
-------------------------------------
I know this is already committed - just a quick question for posterity: what's
the motivation to shell out to "kinit -R" rather than using
KerberosTicket.renew()? Is the goal that we want to keep the ticket cache up to
date rather than just renewing the ticket "in RAM" for some reason?
> Security framework needs to renew Kerberos tickets while the process is
> running
> -------------------------------------------------------------------------------
>
> Key: HADOOP-6656
> URL: https://issues.apache.org/jira/browse/HADOOP-6656
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Devaraj Das
> Fix For: 0.22.0
>
> Attachments: 6656-trunk-1.patch, 6656-trunk-2.patch,
> 6656-trunk-3.patch, 6656-trunk-4.patch, 6656-trunk-4.patch,
> 6656-trunk-4.patch, 6656-trunk-4.patch, c-6656-y20-internal.patch,
> refresh.patch
>
>
> While a client process is running, there should be a thread that periodically
> renews the Kerberos credentials to ensure they don't expire.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
