Skip to content

Commit 77c84f7

Browse files
committed
Address review feedback
1 parent 870a7b8 commit 77c84f7

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

articles/purview/register-scan-hdfs.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -63,15 +63,15 @@ On the **Register sources (HDFS)** screen, follow these steps:
6363

6464
1. Finish to register the data source.
6565

66-
:::image type="content" source="media/register-scan-hdfs/register-sources.png" alt-text="register HDFS source" border="true":::
66+
:::image type="content" source="media/register-scan-hdfs/register-sources.png" alt-text="Screenshot of HDFS source registration in Purview." border="true":::
6767

6868
## Scan
6969

7070
Follow the steps below to scan HDFS to automatically identify assets. For more information about scanning in general, see our [introduction to scans and ingestion](concept-scans-and-ingestion.md).
7171

7272
### Authentication for a scan
7373

74-
The supported authentication type for a HDFS source is **Kerberos authentication**.
74+
The supported authentication type for an HDFS source is **Kerberos authentication**.
7575

7676
### Create and run scan
7777

@@ -96,7 +96,7 @@ To create and run a new scan, follow these steps:
9696
* Provide the user name in the format of `<username>@<domain>.com` in the User name input field. Learn more from [Use Kerberos authentication for the HDFS connector](#use-kerberos-authentication-for-the-hdfs-connector).
9797
* Store the user password used to connect to HDFS in the secret key.
9898

99-
:::image type="content" source="media/register-scan-hdfs/scan.png" alt-text="set up HDFS scan" border="true":::
99+
:::image type="content" source="media/register-scan-hdfs/scan.png" alt-text="Screenshot of HDFS scan configurations in Purview." border="true":::
100100

101101
1. Select **Test connection**.
102102

@@ -270,31 +270,31 @@ Kadmin> addprinc <username>@<REALM.COM>
270270
271271
3. Select the encryption algorithm that's used in Kerberos.
272272

273-
a. Select **Server Manager** > **Group Policy Management** > **Domain** > **Group Policy Objects** > **Default or Active Domain Policy**, and then select **Edit**.
273+
1. Select **Server Manager** > **Group Policy Management** > **Domain** > **Group Policy Objects** > **Default or Active Domain Policy**, and then select **Edit**.
274274

275-
b. On the **Group Policy Management Editor** pane, select **Computer Configuration** > **Policies** > **Windows Settings** > **Security Settings** > **Local Policies** > **Security Options**, and then configure **Network security: Configure Encryption types allowed for Kerberos**.
275+
1. On the **Group Policy Management Editor** pane, select **Computer Configuration** > **Policies** > **Windows Settings** > **Security Settings** > **Local Policies** > **Security Options**, and then configure **Network security: Configure Encryption types allowed for Kerberos**.
276276

277-
c. Select the encryption algorithm you want to use when you connect to the KDC server. You can select all the options.
277+
1. Select the encryption algorithm you want to use when you connect to the KDC server. You can select all the options.
278278

279-
:::image type="content" source="media/register-scan-hdfs/config-encryption-types-for-kerberos.png" alt-text="Screenshot of the &quot;Network security: Configure encryption types allowed for Kerberos&quot; pane":::
279+
:::image type="content" source="media/register-scan-hdfs/config-encryption-types-for-kerberos.png" alt-text="Screenshot of the Network security: Configure encryption types allowed for Kerberos pane.":::
280280

281-
d. Use the `Ksetup` command to specify the encryption algorithm to be used on the specified realm.
281+
1. Use the `Ksetup` command to specify the encryption algorithm to be used on the specified realm.
282282

283283
```cmd
284284
C:> ksetup /SetEncTypeAttr REALM.COM DES-CBC-CRC DES-CBC-MD5 RC4-HMAC-MD5 AES128-CTS-HMAC-SHA1-96 AES256-CTS-HMAC-SHA1-96
285285
```
286286

287287
4. Create the mapping between the domain account and the Kerberos principal, so that you can use the Kerberos principal in the Windows domain.
288288

289-
a. Select **Administrative tools** > **Active Directory Users and Computers**.
289+
1. Select **Administrative tools** > **Active Directory Users and Computers**.
290290

291-
b. Configure advanced features by selecting **View** > **Advanced Features**.
291+
1. Configure advanced features by selecting **View** > **Advanced Features**.
292292

293-
c. On the **Advanced Features** pane, right-click the account to which you want to create mappings and, on the **Name Mappings** pane, select the **Kerberos Names** tab.
293+
1. On the **Advanced Features** pane, right-click the account to which you want to create mappings and, on the **Name Mappings** pane, select the **Kerberos Names** tab.
294294

295-
d. Add a principal from the realm.
295+
1. Add a principal from the realm.
296296

297-
:::image type="content" source="media/register-scan-hdfs/map-security-identity.png" alt-text="Screenshot of the &quot;Security Identity Mapping&quot; pane":::
297+
:::image type="content" source="media/register-scan-hdfs/map-security-identity.png" alt-text="Screenshot of the Security Identity Mapping pane.":::
298298

299299
**On the self-hosted integration runtime machine:**
300300

0 commit comments

Comments
 (0)