Updating VMware Identity Manager hostname in an existing vIDM authentication source configuration within Aria Operations gives the following error 'vIDM source already exists. Delete one before adding a new source.'

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When vIDM is deployed in a clustered environment, updating the existing vIDM hostname to point to either the primary or secondary node instead of the VIP within Aria Operations might cause the authentication source to disappear, displaying "No import source added" as shown in the screenshot below

Re-adding the vIDM authentication source results in the following error. "vIDM source already exists. Delete one before adding a new source."

Environment

Aria Operations 8.18.x
VMware Identity Manager 3.3.7

Resolution

Note : As a precaution, please take snapshots of all the Aria Operations nodes without the memory.

Re-trust Aria Operations with Identity Manager using Aria Suite Lifecycle by following these steps:

• Login to Aria Suite Lifecycle with local admin user.
• Go to Environment > Aria Operations
• Click on Re-trust with Identity Manager under the Ellipse icon menu.
• Once the above task is successful, vIDM authentication will show up under the authentication source
  
  

• Update the vIDM authentication source by changing the vIDM's hostname to either its VIP name or IP address. Ensure the "TEST" connection is successful, then click OK.

• Aria Operations should now be able to authenticate with vIDM.