Unable to import the vIDM certificate when configuring vIDM as an authentication source in Aria Operations

Products

• VMware
• VMware Aria Suite

Issue/Introduction

Configuring vIDM as an authentication source in Aria Operations or Editing a previously working vIDM authentication source can fail to import the identity manager certificate, resulting in a loop and being continuously prompted to accept the certificate.

Symptoms:

Unable to integrate Aria Operations (AOps) authentication source integration with VMware Identity Manager (vIDM).

The analytics-latest.log on one of the analytics nodes will show a warning similar to the following:

• WARN  [ServerConnection on port 10000 Thread 13]  com.vmware.vcops.auth.server.UserAuthenticationServer.testVidmConnection - Request body has invalid content - bad json format or 'issue token' field is missing. :: Request data is not acceptable. - Invalid UTF-8 middle byte 0x72
• Possible variations of the error:
  • Request data is not acceptable. - Unexpected character ('"' (code 34)): was expecting comma to separate Object entries

Environment

Aria Operations 8.18.x
Aria Operations 8.16.x
Aria Operations 8.14.x
Aria Operations 8.12.x

Cause

The problem is with the vIDM password of the user used in the configuration page. The password contains a special character such as " or / which prevent accepting the certificate.

Avoid using special characters such as { } | \ ^ " ] [ ` or /

 

Resolution

No resolution at this time.

Workaround:

Please create a password without using a special character and once its changed it will allow to add the certificates to the Aria Operations.

Avoid using special characters such as { } | \ ^ " ] [ ` or /

Additional Information

"/" (forward slash symbol) will consider rest of the characters as next line in the JSON file.

Impact/Risks:

Unable to add or edit the Identity manager as the authentication source in Aria Operations (AOps).