Unable to authenticate against VMware Aria Suite Lifecycle Health API using VIDM Active Directory accounts

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Accessing the VMware Aria Suite Lifecycle Health Status Check API (/lcm/health/api/v2/status) fails when attempting to authenticate with an VIDM Active Directory account.

• The API successfully authenticates when using the default admin@local account with Basic (base64) authentication.

Environment

VMware Aria Suite Lifecycle 8.x

Cause

According to the VMware Aria Suite Lifecycle architecture, LDAP/vIDM Active Directory based access is not supported by design for the Health API endpoint.

Resolution

While vIDM Active Directory based access is not supported, local users can access the API similarly to the admin@local account if they are assigned the proper roles. To allow a specific user to access the LCM APIs using Basic Authentication, you must assign them the LCM Cloud Admin role.

Steps to assign the LCM Cloud Admin role:

1. Log in to the VMware Aria Suite Lifecycle UI.

2. Navigate to Identity & Tenant Management > User Management.

3. Select the target VIDM local user from the list and click Edit.

4. In the Edit Roles wizard, remove the current restricted roles and select the LCM Cloud Admin role.

5. Click Update.

Once the role is updated, the user will be able to successfully query the Health Status API using Basic Authentication.

Note: Due to a known issue in Aria Suite Lifecycle versions older than 8.18 Patch 7, local users will not be able to run this health status check API. This is expected to be resolved in upcoming releases.

Subscribe to this article to be updated on any changes to fix status: How to Subscribe to Knowledge Articles.

Additional Information

Refer the VMware Aria Suite Lifecycle 8.x health status API documentation at Developer Broadcom Aria Suite Lifecycle Manager API