You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Biju Nair (JIRA)" <ji...@apache.org> on 2018/12/17 15:00:00 UTC
[jira] [Comment Edited] (PHOENIX-5067) Support for secure Phoenix
cluster in Pherf
[ https://issues.apache.org/jira/browse/PHOENIX-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723043#comment-16723043 ]
Biju Nair edited comment on PHOENIX-5067 at 12/17/18 2:59 PM:
--------------------------------------------------------------
{quote}
Kerberos stuff also requires the setting of krb5.conf. Are we expecting that users do kinit manually before they do this?
{quote}
To connect to Kerberos KDC, {{krb5.conf}} need to be configured on the machine from which {{Pherf}} is run. By passing in the Keytab and Principal Phoenix will perform the {{kinit}}.
was (Author: gsbiju):
{quote}
Kerberos stuff also requires the setting of krb5.conf. Are we expecting that users do kinit manually before they do this?
{quote}
To connect to Kerberos KDC, {{krb5.conf}} need to be installed on the machine from which {{Pherf}} is run. By passing in the Keytab and Principal Phoenix will perform the {{kinit}}.
> Support for secure Phoenix cluster in Pherf
> -------------------------------------------
>
> Key: PHOENIX-5067
> URL: https://issues.apache.org/jira/browse/PHOENIX-5067
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Biju Nair
> Assignee: Biju Nair
> Priority: Minor
> Attachments: PHOENIX-5067-4.x-HBase-1.1
>
>
> Currently Phoenix performance and functional testing tool {{Pherf}} doesn't have options to pass in Kerberos principal and Keytab to connect to a secure (Kerberized) Phoenix cluster. This prevents running the tool against a Kerberized clusters.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)