mirror of
https://github.com/apache/impala.git
synced 2025-12-19 09:58:28 -05:00
d484d2f684
This now gives a clean RAT check with bin/check-rat-report.py, which is one way for the Impala community to check compliance with ASF rules on intellectual property. Change-Id: I2ad06435f84a65ba126759e42a18fdaf52cd7036 Reviewed-on: http://gerrit.cloudera.org:8080/5232 Reviewed-by: Jim Apple <jbapple-impala@apache.org> Tested-by: Impala Public Jenkins Reviewed-by: John Russell <jrussell@cloudera.com>
65 lines
2.8 KiB
XML
65 lines
2.8 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!--
|
|
Licensed to the Apache Software Foundation (ASF) under one
|
|
or more contributor license agreements. See the NOTICE file
|
|
distributed with this work for additional information
|
|
regarding copyright ownership. The ASF licenses this file
|
|
to you under the Apache License, Version 2.0 (the
|
|
"License"); you may not use this file except in compliance
|
|
with the License. You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing,
|
|
software distributed under the License is distributed on an
|
|
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
KIND, either express or implied. See the License for the
|
|
specific language governing permissions and limitations
|
|
under the License.
|
|
-->
|
|
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
|
|
<concept id="mixed_security">
|
|
|
|
<title>Using Multiple Authentication Methods with Impala</title>
|
|
<prolog>
|
|
<metadata>
|
|
<data name="Category" value="Security"/>
|
|
<data name="Category" value="Impala"/>
|
|
<data name="Category" value="Authentication"/>
|
|
<data name="Category" value="Kerberos"/>
|
|
<data name="Category" value="LDAP"/>
|
|
<data name="Category" value="Administrators"/>
|
|
</metadata>
|
|
</prolog>
|
|
|
|
<conbody>
|
|
|
|
<p>
|
|
Impala 2.0 and later automatically handles both Kerberos and LDAP authentication. Each
|
|
<cmdname>impalad</cmdname> daemon can accept both Kerberos and LDAP requests through the same port. No
|
|
special actions need to be taken if some users authenticate through Kerberos and some through LDAP.
|
|
</p>
|
|
|
|
<p>
|
|
Prior to Impala 2.0, you had to configure each <cmdname>impalad</cmdname> to listen on a specific port
|
|
depending on the kind of authentication, then configure your network load balancer to forward each kind of
|
|
request to a DataNode that was set up with the appropriate authentication type. Once the initial request was
|
|
made using either Kerberos or LDAP authentication, Impala automatically handled the process of coordinating
|
|
the work across multiple nodes and transmitting intermediate results back to the coordinator node.
|
|
</p>
|
|
|
|
<!--
|
|
<p>
|
|
This technique is most suitable for larger clusters, where
|
|
you are already using load balancing software for high availability.
|
|
You configure Impala to run on a different port on the nodes configured for LDAP.
|
|
Then you configure the load balancing software to forward Kerberos
|
|
connection requests to nodes using the default port, and LDAP connection requests
|
|
to nodes using an alternative port for LDAP.
|
|
Consult the documentation for your load balancing software for how to
|
|
configure that type of forwarding.
|
|
</p>
|
|
-->
|
|
</conbody>
|
|
</concept>
|