Unable to integrate Aria Operations for logs in Aria Operations using vIDM

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When integrating Aria Operations for Logs in Aria Operations using vIDM, the vIDM username format '[email protected]@domain.com' cannot handled by the Aria Operations for Logs API.
The Aria Operations for Logs API wrongly interprets a vIDM username when contains a second or multiple '@' signs.

 

After verifying the configuration and credentials, the following error message appear:

Operations for Logs authentication failed. Invalid credentials.

Environment

Aria Operations 8.16.x
Aria Operations 8.17.x
Aria Operations 8.18.x

 

Resolution

The workaround is to use a username without the '@' sign when authenticating with vIDM.

• This issue was replicated only if the vIDM environment is set up with a username format that is username@domain

• This issue was NOT replicated if the vIDM environment is set up with a username format that is username

 

To conclude, customers are still able to integrate the Aria Operations for Logs in Aria Operations with the vIDM username format: username.
If the customer needs to use the vIDM username format 'username@domain', they will encounter this issue during the integration between Aria Operations and Aria Operations for Logs MP.

Note: For a vIDM environment setup with a username format: username@domain, the format username@domain@domain@authSource can be used for the integration, where authSource is the "Source Display Name" of the VIDM identity source configured in Aria Operations.

Please see the documentation 'Requirements for Integrating With VMware Aria Operations' for other ways to integrate both appliances without using vIDM.

 

Broadcom engineering is aware of the issue and will fix it in an upcoming release of Aria Operations for Logs