Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D67AC200CAD for ; Wed, 28 Jun 2017 08:58:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D5156160BFA; Wed, 28 Jun 2017 06:58:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 29768160BE8 for ; Wed, 28 Jun 2017 08:58:10 +0200 (CEST) Received: (qmail 51797 invoked by uid 500); 28 Jun 2017 06:58:09 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 51779 invoked by uid 99); 28 Jun 2017 06:58:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jun 2017 06:58:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 649B5189100 for ; Wed, 28 Jun 2017 06:58:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id LXalKDsroabH for ; Wed, 28 Jun 2017 06:58:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 2E8395FDE4 for ; Wed, 28 Jun 2017 06:58:07 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A2A74E0DD6 for ; Wed, 28 Jun 2017 06:58:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 0E05924185 for ; Wed, 28 Jun 2017 06:58:02 +0000 (UTC) Date: Wed, 28 Jun 2017 06:58:02 +0000 (UTC) From: "Steen Manniche (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18243) HBase Thrift server lacks logic for renewing kerberos tickets MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 28 Jun 2017 06:58:11 -0000 [ https://issues.apache.org/jira/browse/HBASE-18243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066014#comment-16066014 ] Steen Manniche commented on HBASE-18243: ---------------------------------------- Starting the thrift server with a {{jaas}} configuration file which has instructions to not use a ticket cache ({{useTicketCache=false}}, but instead use a keytab ({{useKeyTab=true}} and values for {{keyTab}} and {{principal}}) seems to have solved the problem for us. However, I do not see any log-files from the {{UserGroupInformation#reloginFromTicketCache}}, which allegedly should be handling the kerberos ticket renewal for the thrift server? > HBase Thrift server lacks logic for renewing kerberos tickets > ------------------------------------------------------------- > > Key: HBASE-18243 > URL: https://issues.apache.org/jira/browse/HBASE-18243 > Project: HBase > Issue Type: Bug > Components: Thrift > Affects Versions: 2.0.0, 1.1.2 > Reporter: Steen Manniche > Priority: Minor > Labels: security > > I have been looking through the hbase-thrift code looking for where > the server performs renewals of kerberos tickets for the provided > principal/keytab. There seems to be no logic in place for renewing tickets. > The hadoop-common provides the class > UserGroupInformation, which exposes the method > {{checkTGTAndReloginFromKeytab}}. I can see that the {{ThriftServerRunner}} class > has a handle to the class > (https://github.com/apache/hbase/blob/master/hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServerRunner.java#L205), > but I do not see the ticket renewal logic being called anywhere. > A possible workaround is to renew the ticket outside the java process. > The documentation on the {{checkTGTAndReloginFromKeytab}} states that if the ticket is still valid, a call to the method is essentially a no-op. -- This message was sent by Atlassian JIRA (v6.4.14#64029)