accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3582) Create workaround for idle shell password prompt with Kerberos
Date Thu, 12 Feb 2015 22:44:12 GMT

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

Josh Elser commented on ACCUMULO-3582:
--------------------------------------

bq. So, the shell knows it started without requiring a password. Not sure how it knew to use
Kerberos instead of to prompt for a password (because it doesn't know how the server side
is configured)

The ClientConfiguration.

bq. presumably, it should be easy to set a flag (or set the timeout to Long.MAX_VALUE) to
skip this.

This was my thought. If the local TGT cache goes away, the user will stop being able to communicate
with Accumulo, so I don't think that setting an infinite timeout has any downsides WRT to
the password-based approach.

> Create workaround for idle shell password prompt with Kerberos
> --------------------------------------------------------------
>
>                 Key: ACCUMULO-3582
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3582
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> When I log into the shell and leave it open, eventually I'll get a password prompt to
re-login.
> This isn't valid for Kerberos-based logins. Come up with a solution.



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

Mime
View raw message