hawq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yo...@apache.org
Subject incubator-hawq-docs git commit: minor edits from last week
Date Mon, 27 Mar 2017 16:32:11 GMT
Repository: incubator-hawq-docs
Updated Branches:
  refs/heads/feature/ranger-integration d84723fae -> 70693401a


minor edits from last week


Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/70693401
Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/70693401
Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/70693401

Branch: refs/heads/feature/ranger-integration
Commit: 70693401a56b53475a425798d71bd40125fa7eb0
Parents: d84723f
Author: David Yozie <yozie@apache.org>
Authored: Mon Mar 27 09:27:57 2017 -0700
Committer: David Yozie <yozie@apache.org>
Committed: Mon Mar 27 09:32:04 2017 -0700

----------------------------------------------------------------------
 markdown/ranger/ranger-integration-config.html.md.erb | 4 ++--
 markdown/ranger/ranger-overview.html.md.erb           | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/70693401/markdown/ranger/ranger-integration-config.html.md.erb
----------------------------------------------------------------------
diff --git a/markdown/ranger/ranger-integration-config.html.md.erb b/markdown/ranger/ranger-integration-config.html.md.erb
index 6a6a4b3..692a729 100644
--- a/markdown/ranger/ranger-integration-config.html.md.erb
+++ b/markdown/ranger/ranger-integration-config.html.md.erb
@@ -19,7 +19,7 @@ software distributed under the License is distributed on an
 KIND, either express or implied.  See the License for the
 specific language governing permissions and limitations
 under the License.
--->
+-->
 
 Your HAWQ 2.2.0 installation includes the following HAWQ-related Ranger components:
 
@@ -30,7 +30,7 @@ The Ranger Administrative UI is installed when you install HDP. You configure
th
 
 Installing or upgrading to HAWQ 2.2.0 installs the HAWQ Ranger Plug-in Service, but neither
configures nor registers the plug-in.  
 
-In order to use Ranger for managing HAWQ authentication events, you must first install and
register several HAWQ JAR files on the Ranger Administration host. This is a one-time configuration
that establishes connectivity to your HAWQ cluster from the Ranger Administration host. After
you have installed the JAR files, you enable or disable Ranger integration in HAWQ by setting
the `hawq_acl_type` configuration parameter.
+In order to use Ranger for managing HAWQ authentication events, you must first install and
register several HAWQ JAR files on the Ranger Administration host. This is a one-time configuration
that establishes connectivity to your HAWQ cluster from the Ranger Administration host. After
you have registered the JAR files, you enable or disable Ranger integration in HAWQ by setting
the `hawq_acl_type` configuration parameter. After Ranger integration is enabled, you must
use the Ranger interface to create all security policies to manage access to HAWQ resources.
Ranger is pre-populated only with several policies to allow `gpadmin` superuser access to
default resources. See [Creating HAWQ Authorization Policies in Ranger](ranger-policy-creation.html)
for information about creating policies in Ranger.
 
 The following procedures describe each configuration activity.
 

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/70693401/markdown/ranger/ranger-overview.html.md.erb
----------------------------------------------------------------------
diff --git a/markdown/ranger/ranger-overview.html.md.erb b/markdown/ranger/ranger-overview.html.md.erb
index b726a85..c5e1cd9 100644
--- a/markdown/ranger/ranger-overview.html.md.erb
+++ b/markdown/ranger/ranger-overview.html.md.erb
@@ -21,13 +21,13 @@ specific language governing permissions and limitations
 under the License.
 -->
 
-HAWQ supports using Apache Ranger for authorizing user access to HAWQ resources. Using Ranger
enables you to manage all of your Hadoop components' authorization policies using a single
user interface, policy store, and auditing store.
+HAWQ supports using Apache Ranger for authorizing user access to HAWQ resources. Using Ranger
enables you to manage all of your Hadoop components' authorization policies using the same
user interface, policy store, and auditing stores.
 
 
 ## <a id="arch"></a>Policy Management Architecture
 Each HAWQ installation includes a Ranger plug-in service to support Ranger Policy management.
The Ranger plug-in service implements the Ranger REST API to bridge all requests between the
Ranger Policy Manager and a HAWQ instance. 
 
-HAWQ also provides a JAR library that enables the Ranger Policy Manager to lookup HAWQ metadata
(for example database, schema, and table names) to populate the user interface and assist
in creating new policies. This JAR uses a JDBC connection to HAWQ, and requires a one-time
registration with the Ranger Policy Manager. See [Configuring HAWQ to use Ranger Policy Management](ranger-integration-config.html#enable).

+HAWQ also provides a JAR library that enables the Ranger Policy Manager to lookup HAWQ metadata
(the names of databases, schemas, tables, and so forth) to populate the user interface and
assist in creating new policies. This JAR uses a JDBC connection to HAWQ, and requires a one-time
registration with the Ranger Policy Manager. See [Configuring HAWQ to use Ranger Policy Management](ranger-integration-config.html#enable).

 
 A single configuration parameter, `hawq_acl_type` determines whether HAWQ defers all policy
management to Ranger via the plug-in service, or whether HAWQ handles authorization natively
using catalog tables. By default, HAWQ uses SQL commands to create all access policies, and
the policy information is stored in catalog tables.  When you enable Ranger integration for
policy management, any authorization policies that you have configured in HAWQ using SQL no
longer apply to your installation; you must create new policies using the Ranger interface.
See [Creating HAWQ Authorization Policies in Ranger](ranger-policy-creation.html)
 


Mime
View raw message