tencent cloud

Elastic MapReduce

Release Notes and Announcements
Release Notes
Announcements
Security Announcements
Product Introduction
Overview
Strengths
Architecture
Features
Use Cases
Constraints and Limits
Technical Support Scope
Product release
Purchase Guide
EMR on CVM Billing Instructions
EMR on TKE Billing Instructions
EMR Serverless HBase Billing Instructions
Getting Started
EMR on CVM Quick Start
EMR on TKE Quick Start
EMR on CVM Operation Guide
Planning Cluster
Administrative rights
Configuring Cluster
Managing Cluster
Managing Service
Monitoring and Alarms
TCInsight
EMR on TKE Operation Guide
Introduction to EMR on TKE
Configuring Cluster
Cluster Management
Service Management
Monitoring and Ops
Application Analysis
EMR Serverless HBase Operation Guide
EMR Serverless HBase Product Introduction
Quotas and Limits
Planning an Instance
Managing an Instance
Monitoring and Alarms
Development Guide
EMR Development Guide
Hadoop Development Guide
Spark Development Guide
Hbase Development Guide
Phoenix on Hbase Development Guide
Hive Development Guide
Presto Development Guide
Sqoop Development Guide
Hue Development Guide
Oozie Development Guide
Flume Development Guide
Kerberos Development Guide
Knox Development Guide
Alluxio Development Guide
Kylin Development Guide
Livy Development Guide
Kyuubi Development Guide
Zeppelin Development Guide
Hudi Development Guide
Superset Development Guide
Impala Development Guide
Druid Development Guide
TensorFlow Development Guide
Kudu Development Guide
Ranger Development Guide
Kafka Development Guide
Iceberg Development Guide
StarRocks Development Guide
Flink Development Guide
JupyterLab Development Guide
MLflow Development Guide
Practical Tutorial
Practice of EMR on CVM Ops
Data Migration
Practical Tutorial on Custom Scaling
API Documentation
History
Introduction
API Category
Cluster Resource Management APIs
Cluster Services APIs
User Management APIs
Data Inquiry APIs
Scaling APIs
Configuration APIs
Other APIs
Serverless HBase APIs
YARN Resource Scheduling APIs
Making API Requests
Data Types
Error Codes
FAQs
EMR on CVM
Service Level Agreement
Contact Us

Configuring LDAP Authentication

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-10-30 11:35:19
This document introduces the configuration and use of LDAP in Hive on EMR.

Development Preparation

Make sure you have activated Tencent Cloud and created an EMR cluster. For more details, see Creating a Cluster.
Create a Hadoop default scene cluster and select the Hive component in the software configuration interface.

Enabling LDAP Authentication

Enter the EMR console, click Cluster Services > HIVE > Configuration Management, select the hive-site.xml configuration file, add the following configuration items, set parameter values, save the configuration and deploy it, and then restart HiveServer2:
Parameter
Value
Remarks
hive.server2.authentication
LDAP
Set the authentication mechanism to LDAP.
hive.server2.authentication.ldap.url
ldap://$l{dap_ip}:389
Specify the URL for the LDAP service.
${ldap_ip} represents the IP address of the OPENLDAP service node, which can be found under Cluster Services > OPENLDAP in the EMR console.
For a self-built LDAP service, fill in the details according to your actual setup.
hive.server2.authentication.ldap.baseDN
ou=People,dc=emr,dc=cloud,dc=tencent,dc=com
The Base DN where the LDAP service user is located in EMR. For a self-built LDAP service, fill in the details according to your actual setup.
hive.server2.authentication.ldap.guidKey
cn
The LDAP service username format in EMR. For a self-built LDAP service, fill in the details according to your actual setup.

Accessing HiveServer2

After enabling LDAP authentication, you will need to provide the LDAP username and password to access HiveServer2.

Connecting to Hive with Beeline Client

beeline -u "jdbc:hive2://${hs2_ip}:${hs2_port}" -n ${user} -p ${password}

Connecting to Hive with JDBC

jdbc:hive2://${hs2_ip}:${hs2_port}/default;user=${user};password=${password}
Note:
1. ${user} represents the LDAP username.
2. ${password} represents the LDAP password.
3. ${hs2_ip} is the private IP address of the node where the HiveServer2 service is deployed. You can view it on the cluster details page under Cluster Services > Hive > Role Management.
4. ${hs2_port} is the port number of the HiveServer2 in the cluster, with a default value of 7001. You can view it on the cluster details page under Cluster Services > Hive > Configuration Management by checking the hive.server2.thrift.port setting in the hive-site.xml configuration file.
Note:
After integrating Hive with EMR OpenLDAP and adding a new user, grant 644 permissions to the /emr/hive directory under HDFS for the new user to access.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック