AD Sync is not happening in vIDM which is causing login issues to Aria Automation portal.
search cancel

AD Sync is not happening in vIDM which is causing login issues to Aria Automation portal.

book

Article ID: 394855

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • Error in Aria Automation UI : 403 Error it appears that you don't have access

  • vIDM 3.3.7 shows error in the admin portal for the SSH user,"Password for user sshuser has expired"

 

Environment

vIDM  3.3.7

Resolution

  • Create snapshots without memory in VC for all vIDM nodes. 

  • Login as root via SSH on all vIDM node(s).

  • Run this command : passwd sshuser on the all nodes to create a new SSH User password.

  • In Aria Lifecycle add or update the new  SSH and SSH user credentials in the Locker and sync the changes done in vIDM.

  •  Run below command on primary node to increase the OpenSearch max shards count to 6500/8200:

    curl -X PUT localhost:9200/_cluster/settings -H "Content-Type: application/json" -d '{ "persistent":
    { "cluster.max_shards_per_node": "8200" }
    }'  

    source:  AD group are not syncing with Identity Manager and users are able to access Aria Automation.

  • In vIDM, determine current health status, it can being see in the user  interface via command, use the command below: watch curl http://localhost:9200/_cluster/health?pretty=true .  

Note:  In the above command output, Elasticsearch/Opensearch cluster status can be: Red, Yellow, Green.
The health status will flag as Red, If there are a number of UNASSIGNED shards within the cluster. Try steps 3,4,5,6, from KB  After upgrading to vIDM 3.3.7, user dashboard reporting and Active Directory sync log are not updating: the cluster currently has the maximum number of shards open
Sync the groups in vIDM

 

Additional Information

Powered by Wolken Software