Skip to content

Commit 0d7f828

Browse files
committed
freshness65
1 parent 0f81d2f commit 0d7f828

File tree

6 files changed

+22
-22
lines changed

6 files changed

+22
-22
lines changed

articles/hdinsight/hdinsight-sync-aad-users-to-cluster.md

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
22
title: Synchronize Azure Active Directory users to HDInsight cluster
33
description: Synchronize authenticated users from Azure Active Directory to an HDInsight cluster.
4-
ms.service: hdinsight
54
author: ashishthaps
65
ms.author: ashishth
76
ms.reviewer: jasonh
8-
ms.custom: hdinsightactive
7+
ms.service: hdinsight
98
ms.topic: conceptual
10-
ms.date: 09/24/2018
9+
ms.custom: hdinsightactive
10+
ms.date: 11/21/2019
1111
---
1212

1313
# Synchronize Azure Active Directory users to an HDInsight cluster
1414

15-
[HDInsight clusters with Enterprise Security Package (ESP)](hdinsight-domain-joined-introduction.md) can use strong authentication with Azure Active Directory (Azure AD) users, as well as use *role-based access control* (RBAC) policies. As you add users and groups to Azure AD, you can synchronize the users who need access to your cluster.
15+
[HDInsight clusters with Enterprise Security Package (ESP)](hdinsight-domain-joined-introduction.md) can use strong authentication with Azure Active Directory (Azure AD) users, as well as use *role-based access control* (RBAC) policies. As you add users and groups to Azure AD, you can synchronize the users who need access to your cluster.
1616

1717
## Prerequisites
1818

@@ -22,7 +22,7 @@ If you have not already done so, [create a HDInsight cluster with Enterprise Sec
2222

2323
To view your hosts, open the Ambari Web UI. Each node will be updated with new unattended upgrade settings.
2424

25-
1. In the [Azure portal](https://portal.azure.com), navigate to the Azure AD directory associated with your ESP cluster.
25+
1. From the [Azure portal](https://portal.azure.com), navigate to the Azure AD directory associated with your ESP cluster.
2626

2727
2. Select **All users** from the left-hand menu, then select **New user**.
2828

@@ -40,20 +40,20 @@ User groups specified during the cluster creation process are synchronized at th
4040

4141
The following method uses POST with the Ambari REST API. For more information, see [Manage HDInsight clusters by using the Apache Ambari REST API](hdinsight-hadoop-manage-ambari-rest-api.md).
4242

43-
1. [Connect to your cluster with SSH](hdinsight-hadoop-linux-use-ssh-unix.md). From the overview pane for your cluster in the Azure portal, select the **Secure Shell (SSH)** button.
44-
45-
![HDInsight Secure Shell (SSH) icon](./media/hdinsight-sync-aad-users-to-cluster/hdinsight-secure-shell.png)
43+
1. Use [ssh command](hdinsight-hadoop-linux-use-ssh-unix.md) to connect to your cluster. Edit the command below by replacing `CLUSTERNAME` with the name of your cluster, and then enter the command:
4644

47-
2. Copy the displayed `ssh` command and paste it into your SSH client. Enter the ssh user password when prompted.
45+
```cmd
46+
47+
```
4848
49-
3. After authenticating, enter the following command:
49+
1. After authenticating, enter the following command:
5050
5151
```bash
52-
curl -u admin:<YOUR PASSWORD> -sS -H "X-Requested-By: ambari" \
52+
curl -u admin:PASSWORD -sS -H "X-Requested-By: ambari" \
5353
-X POST -d '{"Event": {"specs": [{"principal_type": "groups", "sync_type": "existing"}]}}' \
54-
"https://<YOUR CLUSTER NAME>.azurehdinsight.net/api/v1/ldap_sync_events"
54+
"https://CLUSTERNAME.azurehdinsight.net/api/v1/ldap_sync_events"
5555
```
56-
56+
5757
The response should look like this:
5858
5959
```json
@@ -69,14 +69,14 @@ The following method uses POST with the Ambari REST API. For more information, s
6969
}
7070
```
7171
72-
4. To see the synchronization status, execute a new `curl` command:
72+
1. To see the synchronization status, execute a new `curl` command:
7373
7474
```bash
75-
curl -u admin:<YOUR PASSWORD> https://<YOUR CLUSTER NAME>.azurehdinsight.net/api/v1/ldap_sync_events/1
75+
curl -u admin:PASSWORD https://CLUSTERNAME.azurehdinsight.net/api/v1/ldap_sync_events/1
7676
```
77-
77+
7878
The response should look like this:
79-
79+
8080
```json
8181
{
8282
"href" : "http://hn0-hadoop.YOURDOMAIN.com:8080/api/v1/ldap_sync_events/1",
@@ -115,14 +115,14 @@ The following method uses POST with the Ambari REST API. For more information, s
115115
}
116116
```
117117
118-
5. This result shows that the status is **COMPLETE**, one new user was created, and the user was assigned a membership. In this example, the user is assigned to the "HiveUsers" synchronized LDAP group, since the user was added to that same group in Azure AD.
118+
1. This result shows that the status is **COMPLETE**, one new user was created, and the user was assigned a membership. In this example, the user is assigned to the "HiveUsers" synchronized LDAP group, since the user was added to that same group in Azure AD.
119119
120-
> [!NOTE]
121-
> The previous method only synchronizes the Azure AD groups specified in the **Access user group** property of the domain settings during cluster creation. For more information, see [create an HDInsight cluster](domain-joined/apache-domain-joined-configure.md).
120+
> [!NOTE]
121+
> The previous method only synchronizes the Azure AD groups specified in the **Access user group** property of the domain settings during cluster creation. For more information, see [create an HDInsight cluster](domain-joined/apache-domain-joined-configure.md).
122122
123123
## Verify the newly added Azure AD user
124124
125-
Open the [Apache Ambari Web UI](hdinsight-hadoop-manage-ambari.md) to verify that the new Azure AD user was added. Access the Ambari Web UI by browsing to **`https://<YOUR CLUSTER NAME>.azurehdinsight.net`**. Enter the cluster administrator username and password.
125+
Open the [Apache Ambari Web UI](hdinsight-hadoop-manage-ambari.md) to verify that the new Azure AD user was added. Access the Ambari Web UI by browsing to **`https://CLUSTERNAME.azurehdinsight.net`**. Enter the cluster administrator username and password.
126126
127127
1. From the Ambari dashboard, select **Manage Ambari** under the **admin** menu.
128128
@@ -138,7 +138,7 @@ Open the [Apache Ambari Web UI](hdinsight-hadoop-manage-ambari.md) to verify tha
138138
139139
## Log in to Ambari as the new user
140140
141-
When the new user (or any other domain user) logs in to Ambari, they use their full Azure AD user name and domain credentials. Ambari displays a user alias, which is the display name of the user in Azure AD.
141+
When the new user (or any other domain user) logs in to Ambari, they use their full Azure AD user name and domain credentials. Ambari displays a user alias, which is the display name of the user in Azure AD.
142142
The new example user has the user name `[email protected]`. In Ambari, this new user shows up as `hiveuser3` but the user logs into Ambari as `[email protected]`.
143143
144144
## See also
20.7 KB
Loading
14.6 KB
Loading
13.4 KB
Loading
18.3 KB
Loading

0 commit comments

Comments
 (0)