After changing the SSO Admin password via vRA VAMI, the authentication provider of the embedded vRO is set to default value
book
Article ID: 319579
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
Symptoms:
- Authentication Provider of embedded vRO is set to the default value.
- Some of the vRA services in VAMI console shows as Unavailable and null.
advanced-designer-service - UNAVAILABLE
o11n-gateway-service -UNAVAILABLE
shell-ui-app - UNAVAILABLE
vco - null
- Unable to log in to default tenant for tenant management​.
Environment
VMware vRealize Automation 7.4.x
Resolution
This issue is resolved in VMware vRealize Automation 7.5, available at Broadcom Downloads.
Workaround:
To work around this issue if you do not want to upgrade:
- Log in to primary vRO control center <https://vra-master-appliance:8283/vco-controlcenter> using appliance root credentials.
- Click Configure Authentication Provider.
- Observe that Admin group of authentication Provider is set to the default value (vsphere.local\vcoadmins).
- Click Change button of Admin group and enter previously configured value example: rainpole.local\ug-vROAdmins.
- Click Save changes.
- Log in into VAMI console of the vra-primary-appliance using the appliance root credential.
- On the Services tab, verify the status of all the services is REGISTERED (Periodically refresh the page).
- Proceed to second vRA node and log in to VAMI page.
- Navigate to vRA Settings > Cluster .
- Provide the FQDN and credentials of the primary node and join the cluster.
- Wait for 10 to 15 minutes and check the status of all the services to be Registered.
Note: Repeat step 8 to 11 for all the additional vRA appliances in vRA nodes cluster.
Feedback
thumb_up
Yes
thumb_down
No