Preparation 2: Checking Configuration Based on the Checklist

Checklist

Viewing the guest_agent Version of a GaussDB(DWS) Cluster

1. Log in to the GaussDB (DWS) console, choose Clusters, and locate a cluster.
2. Press F12 to open the developer debugging tool and click the Network tab.
   Figure 1 Network
   

3. Click the name of the cluster to go to the Basic Information page. On the Network tab page, locate and click the long string starting with clusters?type=xxxxxx. In the right pane, click Preview and search for the guest_agent_version field, whose value is the guest_agent version of the GaussDB(DWS) cluster.
   Figure 2 Locating the guest_agent_version field
   

4. If the version is not your required one, contact the customer service or technical support of GaussDB(DWS).

Configuring the Ranger Component

In a non-security MRS cluster, the Ranger component synchronizes Unix users by default, but does not synchronize users, user groups, or roles on FusionInsight Manager. Therefore, you need to switch the user synchronization policy. The procedure is as follows:

By default, the Ranger component of an MRS security cluster synchronizes LDAP users. No additional operation is required. If the default configuration is changed, you can change the user synchronization policy by referring to this section.

1. Log in to MRS Manager as user admin.
2. On the Manager page, choose Cluster > Services > Ranger > Configurations > Basic Configurations, search for ranger.usersync.config.expandor in the search box, and set its name to ranger.usersync.sync.source and value to ldap.
   

   By default, this parameter is unavailable for MRS clusters of old versions (for example, MRS 3.1.0). You can contact the customer service or technical support of MRS for support.

   Figure 3 Configuring the ranger.usersync.config.expandor parameter
   

3. After the parameter is set, click Save in the upper left corner and then OK in the dialog box to save the configuration.
4. After the configuration is saved, switch to the Instances tab page, select the UserSync instance that has expired, click More, and select Instance Rolling Restart to make the configuration take effect.
   Figure 4 Performing a rolling instance restart
   

Preparing a Ranger Admin User

The user for the Ranger connection must have the admin permission of the Ranger component. The procedure is as follows:

1. Log in to MRS Manager as user admin.
2. Choose System > Permission > User. On the page displayed, click Create to add a dedicated user as the Kerberos authentication user. Select user groups superGroup and hive for the user, and assign the Manager_administrator role to the user.
3. Log in to MRS Manager as the new user and change the initial password.
4. On the Manager page, choose Cluster > Services > Ranger. On the Ranger overview page, click RangerAdmin to go to the Ranger WebUI.
   Figure 5 Accessing the Ranger WebUI
   

5. Log out of the current account and use the Ranger administrator account to log in again. For a common cluster, the admin account for the Manager page can be used as the Ranger administrator account. For a security cluster, rangeradmin is the Ranger administrator account. For details about the default password of rangeradmin, see User Account List.
   Figure 6 Logging out of the current account
   

6. Change the role of the new user from Ranger to Admin. Find the name of the new user in Settings > Users/Groups/Roles > Users.
   

   If the new user is not found on Ranger, wait for about five minutes until Ranger automatically synchronizes the MRS cluster role.

   Figure 7 Searching for the username
   

7. Click the username to go to the details page, change the user role to Admin, and click Save.
   Figure 8 Changing the user role