Aria Config IDM integration issue post upgrade to 8.16.2
search cancel

Aria Config IDM integration issue post upgrade to 8.16.2

book

Article ID: 372296

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

After upgrading Aria Automation and Aria Automation Config to 8.16.2 the VMware Identity Manager / Workspace ONE integration with Aria Config no longer works

Environment

Aria Config 8.16.2 and newer

Cause

​​Changes in how Aria Automation integrates with VMware Identity Manager do not allow for proper passthrough of the integration to Aria Automation Config as of version 8.16.2

Resolution

​​The current workaround is to disable the vIDM integration provided by Aria Automation, to do this we remove the identity integration parameters stored by Aria Config in the postgres database

NOTE: This procedure does not break any functional integration between the Automation and Config platforms. Provisioning salt-minions via Aria Automation blueprints will continue to work. This will only effect authentication to the Aria Config web UI, which will fall back to local accounts

    1. Take a snapshot of the Aria Config appliance
    2. Take a backup of the Aria Config database using the document below for guidance:
      1. https://docs.vmware.com/en/VMware-Aria-Automation/8.16/Installing-Automation-Config/GUID-30ED9B88-E2D4-45D1-8976-25889BC84AB2.html
    3. Stop the raas service on the Aria Config server:
      1. SSH into the Aria Config server
      2. systemctl stop raas
    4. Access the postgres database using the psql command:
      1. Example login command: psql -U postgres -h localhost -p 5432
    5. Find the raas database name, connect to the db, and delete the Aria Automation integration parameters:
      1. \l                                          # raas db will be named like "raas_xxxx"
      2. \c raas_43cab1f4de604ab185b51d883c5c5d09    # connects to the raas db
      3. delete from vra_params;                                                                 #   Do not run this without having taken the appropriate backup steps outlined above
    6. Start the raas service
      1. systemctl start raas
    7. Ensure that you are able to login to the Aria Config web UI with the default local user:
      1. username: root
      2. password: salt
    8. If the default user detailed here does not allow you to login please contact support 
    9. Navigate to administration ui to update root password away from default value
    10. Use this administration ui to add and manage local users and groups
    11. You may also leverage Aria Configs ability to integrate directly into an LDAP provider as documented below:
      1. https://docs.vmware.com/en/VMware-Aria-Automation/8.16/Using-Automation-Config/GUID-54FE4409-718B-4BA9-ADD3-7CA1874865F5.html