[
https://issues.apache.org/jira/browse/HAWQ-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086989#comment-16086989
]
ASF GitHub Bot commented on HAWQ-1497:
--------------------------------------
Github user radarwave commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/127#discussion_r127402619
--- Diff: markdown/clientaccess/disable-kerberos.html.md.erb ---
@@ -21,43 +21,49 @@ specific language governing permissions and limitations
under the License.
-->
-Follow these steps to disable Kerberos security for HAWQ and PXF for
manual installations.
+HAWQ supports Kerberos at both the HDFS and/or user authentication levels.
You will perform different disable procedures for each.
-**Note:** If you install or manage your cluster using Ambari, then the
HAWQ Ambari plug-in automatically disables security for HAWQ and PXF when you
disable security for Hadoop. The following instructions are only necessary for
manual installations, or when Hadoop security is disabled outside of Ambari.
-1. Disable Kerberos on the Hadoop cluster on which you use HAWQ.
-2. Disable security for HAWQ:
- 1. Login to the HAWQ database master server as the `gpadmin` user:
+## <a id="disable_kerb_hdfs"></a>Disable Kerberized HDFS for HAWQ/PXF
- ``` bash
- $ ssh hawq_master_fqdn
- ```
+You will perform different procedures to disable HAWQ/PXF access to a
previously-kerberized HDFS depending upon whether you manage your cluster from
the command line or use Ambari to manage your cluster.
+
+### <a id="disable_kerb_hdfs_ambari"></a>Procedure for Ambari-Managed
Clusters
+
+If you manage your cluster using Ambari, you will disable Kerberos
authentication for your cluster as described in the [How To Disable
Kerberos](https://docs.hortonworks.com/HDPDocuments/Ambari-2.4.2.0/bk_ambari-user-guide/content/how_to_disable_kerberos.html)
Hortonworks documentation. Ambari will guide you through the de-kerberization
process, including removing/updating any authentication-related configuration
in your cluster.
- 2. Run the following command to set up HAWQ environment variables:
+### <a id="disable_kerb_hdfs_ambari"></a>Procedure for
Command-Line-Managed Clusters
+
+If you manage your cluster from the command line, follow these
instructions to disable HDFS Kerberos security for HAWQ and PXF.
+
+1. Disable Kerberos on the Hadoop cluster on which you use HAWQ.
+2. Disable security for HAWQ:
+ 1. Login to the HAWQ database master server as the `gpadmin` user and
set up your HAWQ environment:
``` bash
- $ source /usr/local/hawq/greenplum_path.sh
+ $ ssh gpadmin@<master>
+ gpadmin@master$ . /usr/local/hawq/greenplum_path.sh
```
- 3. Start HAWQ if necessary:
+ 2. Start HAWQ if necessary:
``` bash
- $ hawq start -a
+ gpadmin@master$ hawq start cluster -a
--- End diff --
‘hawq start cluster’ do not need '-a' option.
> docs - refactor the kerberos sections
> -------------------------------------
>
> Key: HAWQ-1497
> URL: https://issues.apache.org/jira/browse/HAWQ-1497
> Project: Apache HAWQ
> Issue Type: Improvement
> Components: Documentation
> Reporter: Lisa Owen
> Assignee: David Yozie
>
> the kerberos docs do not really distinguish between enabling kerberos at the
> HDFS filesystem level vs. enabling kerberos user authentication for HAWQ.
> also missing content for config'ing HAWQ/PXF for secure HDFS.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
