From dev-return-54686-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Wed Nov 28 16:23:06 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B8426180677 for ; Wed, 28 Nov 2018 16:23:05 +0100 (CET) Received: (qmail 78878 invoked by uid 500); 28 Nov 2018 15:23:04 -0000 Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list dev@phoenix.apache.org Received: (qmail 78866 invoked by uid 99); 28 Nov 2018 15:23:04 -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 Nov 2018 15:23:04 +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 5DDC6180653 for ; Wed, 28 Nov 2018 15:23:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id hQM83MgAa3sh for ; Wed, 28 Nov 2018 15:23:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3C8D4610D9 for ; Wed, 28 Nov 2018 15:23:02 +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 7FDA9E0E1D for ; Wed, 28 Nov 2018 15:23:00 +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 322DB24DD2 for ; Wed, 28 Nov 2018 15:23:00 +0000 (UTC) Date: Wed, 28 Nov 2018 15:23:00 +0000 (UTC) From: "Biju Nair (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (PHOENIX-5006) jdbc connection to secure cluster should be able to use Kerberos ticket of user MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-5006?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Biju Nair updated PHOENIX-5006: ------------------------------- Attachment: PHOENIX-5006.possiblefix > jdbc connection to secure cluster should be able to use Kerberos ticket o= f user > -------------------------------------------------------------------------= ------ > > Key: PHOENIX-5006 > URL: https://issues.apache.org/jira/browse/PHOENIX-5006 > Project: Phoenix > Issue Type: Bug > Reporter: Biju Nair > Priority: Minor > Attachments: PHOENIX-5006.possiblefix > > > Currently JDBC connection against a secure Phoenix cluster requires a Ker= beros principal and keytab to be passed in as part of the connection string= . But in many instances users may not have a {{Keytab}} especially during d= evelopment. It would be good to support using the logged in users Kerberos = ticket.=C2=A0 > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)