Aria Operations for Logs is not authenticating using Workspace ONE Access (a.k.a vIDM)
search cancel

Aria Operations for Logs is not authenticating using Workspace ONE Access (a.k.a vIDM)

book

Article ID: 402758

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

It has been found that the "Aria Operations for Logs" is failing to authenticate using Workspace One intermittently.

The below steps have been taken to resolve the issue:

  • Updated binding password for Workspace ONE Access and tried syncing. Sync was successful but "Aria Operations for Logs" is failing to authenticate using Workspace ONE Access.
  • Validated cluster, all nodes looks connected.
  • Validated other components in the suite like Aria Operations and authentication is working for the other components.

Environment

Aria Operations for logs 

Workspace One (a.k.a vIDM)

 

Cause

Using an Active Directory account for integration with vIDM

 

File: /storage/core/loginsight/var/runtime.log

[2025-06-15 11:46:35.432+0000] ["CheckPerformer-thread-1"/192.0.2.1 ERROR] [com.vmware.loginsight.aaa.vidm.VIDMConnector] [Could not validate OAuth Access Token info. hostname:example.com, tenant: . null]
jsonResult: {"result":"Workspace ONE Access authentication test failed."}
jsonResult: {"result":"Not using active directory for authentication."}
jsonResult: {"result":"Not using active directory for authentication."}

Resolution

As per the following KB, Workspace One (vIDM) integration can be done only with local users.

Active Directory users who are assigned a tenant admin role are not eligible for integration.  

Integration of Workspace One with Aria Operations for Logs fails with error "Unable to authorize to Workspace ONE Access instance with provided credentials.