Those familiar with deploying VMware vRealize Suite know just how vital VMware Identity Manager (vIDM) is to support the entire deployment. For those who haven’t deployed VMware vRealize Suite, VMware Identity Manager is the centralized authentication platform integrated throughout the entire VMware vRealize Suite of products. It provides multiple directory options, including Active Directory Integrated Windows Authentication, Active Directory over LDAPS, traditional LDAP directories, and local directories. Authentication options include traditional username/password, x509 certificate/smart card, Kerberos, RSA Adaptive Authentication, RSA SecurID, and RADIUS.
While some products within the VMware vRealize Suite such as VMware vRealize Operations and VMware vRealize Log Insight support local authentication and Active Directory integration natively, VMware vRealize Automation 8.x depends exclusively on VMware Identity Manager to provide authentication services. With VMware vRealize Automation 8.x being the foundation of many private cloud environments, the availability of VMware Identity Manager becomes crucial.
In this article, I walk you through the process of configuring the VMware vRealize Operations Management Pack for VMware Identity Manager 1.3.1 and the capabilities that it provides. The management pack supports VMware vRealize Operations 8.4 through 8.6.x, Advanced and Enterprise editions. I am utilizing VMware vRealize Operations 8.6.2 Enterprise and VMware Identity Manager 3.3.6 to create this walkthrough.
The first step is installing the VMware vRealize Operations Management Pack for VMware Identity Manager 1.3.1 within VMware vRealize Operations. The process of installing a new management pack to VMware vRealize Operations is very straightforward, as documented here: VMware vRealize Operations 8.6 – Adding Solutions. Once you have the management pack installed, it is time to connect it to your deployment of VMware Identity Manager.
This connection requires an account that is either part of the Super Admin or ReadOnly Admin roles within VMware Identity Manager. In my deployment, I configured an account just for this purpose. I assigned it the ReadOnly Admin role as the account should not be able to do anything other than view the health of the VMware Identity Manager deployment. To create this account, you will need to access the VMware Identity Manager Admin interface by pointing your browser to “https://{FQDN of vIDM Instance}/SAAS/admin” replacing {FQDN of vIDM Instance} with the hostname of your VMware Identity Manager deployment. Log in to the interface using an account assigned to the Super Admin role, such as the built-in “admin” account. Next, select the “Users and Groups” tab from the top of the page, then click the “Add User Button.”
On the resulting “Add a user” dialog, enter the details for your service account. Since we are creating a local service account, select “System Directory” from the “Directory List” and “System Domain” from the “Domain List.” Enter the username for the new account, and then enter an email address that you have access to (you will receive an email that allows you to set the password). Provide a value for the “First Name” and “Last Name” fields, then select “ReadOnly Admin” from the “Role” list.
Please note that you must have SMTP configured within your VMware Identity Manager deployment to send you the email allowing you to set the password. If you cannot configure SMTP, you can set the account password using the REST API as documented here: Reset local user password in VMware Identity Manager vIDM via REST API using Postman. Additionally, you can import an account from an external directory such as Active Directory to utilize as the service account. If you are setting the password from the email message sent, be sure that you log out from VMware Identity Manager before accessing the link or open the link using an Incognito or InPrivate browser session.
Now that you have an account within VMware Identity Manager, the next step in this process is to connect VMware vRealize Operations to your VMware Identity Manager instances. To do this, log in to your VMware vRealize Operations instance using an account that has all of the “Datasource” permissions assigned. Next, select “Data Sources” and then “Integrations” from the left side navigation. To add our new integration, click the “Add Account” button.
You are presented with the “Account Types” selection screen. From here, look for the item labeled “VMware Identity Manager.” Click on this box to move to the next screen.
Next, we provide the details on connecting our deployment of VMware Identity Manager. The “Name” field is how VMware vRealize Operations will present the deployment within the application. I usually specify the FQDN for this field. The “vIDM Host” field should contain the FQDN to your VMware Identity Manager deployment. Enter the load-balanced FQDN to the deployments if you have a highly available deployment. In the “Credentials” field, click the “+” beside the field to add a new set of credentials. After defining the credentials, make sure your new entry is selected. Finally, click the “Save” button to save the configuration.
After saving the new integration, verify that the integration is connected and collecting data by expanding the “VMware Identity Manager Adapter” entry on the “Integrations” page and looking for the green “OK” status.
The VMware vRealize Operations Management Pack for VMware Identity Manager 1.3.1 contains some initial content to help you get started with monitoring your VMware Identity Manager environments. This includes a single overview dashboard and several symptom/alert definitions.
The single dashboard included with the management pack provides a high-level overview of your VMware Identity Manager deployments. The top portion of the dashboard provides an overview list of all registered VMware Identity Manager deployments, including Name, FQDN, IP, Number of Active Users, Number of Directories, Number of LDAP Directories, Number of Local Directories, Version, Current Time, and Health. The bottom portion of the dashboard provides a drill-down of details for the specific environment selected from the top part of the dashboard. Details included in this drill down are Total Apps, Total Devices, Total Groups, Total Users, All Activity, Groups Removed, Groups Updated, Users Added, Unique User Logins, and Health.
In addition to the included dashboard, the management pack also contains 21 symptom definitions and 17 alert definitions.
The symptom definitions included are the following:
The alert definitions included are the following:
The management pack includes several metrics and properties for the various objects discovered/monitored. Because the list is quite long, I will refer you to VMware’s official documentation. However, I have noticed that a few metrics are missing from this documentation, but overall, it’s a detailed list. Metrics in VMware Identity Manager
The SDDC Health Monitoring Solution for vRealize Operations is a valuable tool for seeing a complete picture of your software-defined data center’s health. After you complete the setup of the VMware vRealize Operations Management Pack for VMware Identity Manager, the SDDC Health Monitoring Solution for VMware vRealize Operations will surface health information and relationships related to VMware Identity Manager within the SDDC Management Health Overview dashboard.
The VMware vRealize Operations Management Pack for VMware Identity provides a lot of great out-of-the-box information that can give you a quick way to begin monitoring VMware Identity Manager. It’s great that it automatically integrates with the SDDC Health Monitoring Solution to provide a quick high-level view of your SDDC health. However, I feel that the management pack lacks some polish and depth:
It would be great if the management pack could provide:
Search
Get Notified of Future Posts
Recent Posts