Skip to content

Commit 459719e

Browse files
committed
HADOOP-18627 Stronger wording in 'secure mode' intro
Make it more clear that when exposing Hadoop to untrusted users, 'secure mode' is not optional.
1 parent 17c8cdf commit 459719e

File tree

1 file changed

+3
-1
lines changed
  • hadoop-common-project/hadoop-common/src/site/markdown

1 file changed

+3
-1
lines changed

hadoop-common-project/hadoop-common/src/site/markdown/SecureMode.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,9 @@ Hadoop in Secure Mode
2020
Introduction
2121
------------
2222

23-
This document describes how to configure authentication for Hadoop in secure mode. When Hadoop is configured to run in secure mode, each Hadoop service and each user must be authenticated by Kerberos.
23+
In its default configuration, we expect you to make sure attackers don't have access to your Hadoop deployment by restricting all network access. If you want to expose Hadoop to untrusted users, you will have to configure authentication for Hadoop in secure mode as described in this document.
24+
25+
When Hadoop is configured to run in secure mode, each Hadoop service and each user must be authenticated by Kerberos.
2426

2527
Forward and reverse host lookup for all service hosts must be configured correctly to allow services to authenticate with each other. Host lookups may be configured using either DNS or `/etc/hosts` files. Working knowledge of Kerberos and DNS is recommended before attempting to configure Hadoop services in Secure Mode.
2628

0 commit comments

Comments
 (0)