You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Lin Wen (JIRA)" <ji...@apache.org> on 2016/08/31 06:15:20 UTC
[jira] [Commented] (HAWQ-845) Parameterize kerberos principal name
for HAWQ
[ https://issues.apache.org/jira/browse/HAWQ-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451291#comment-15451291 ]
Lin Wen commented on HAWQ-845:
------------------------------
For now I think we can keep 'postgres' as default kerberos service name, but customers should be able to parameterize it with other name.
If user want to use a different name, below property/value should be added into hawq-site.xml
<property>
<name>krb_srvname</name>
<value>gpadmin</value>
</property>
> Parameterize kerberos principal name for HAWQ
> ---------------------------------------------
>
> Key: HAWQ-845
> URL: https://issues.apache.org/jira/browse/HAWQ-845
> Project: Apache HAWQ
> Issue Type: Improvement
> Reporter: bhuvnesh chaudhary
> Assignee: Lei Chang
> Priority: Minor
> Fix For: backlog
>
>
> Currently HAWQ only accepts the principle 'postgres' for kerberos settings.
> This is because it is hardcoded in gpcheckhdfs, we should ensure that it can be parameterized.
> Also, it's better to change the default principal name postgres to gpadmin. It will avoid the need of changing the the hdfs directory during securing the cluster to postgres and will avoid the need of maintaining postgres user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)