On our VMware Cloud Provider Partner Slack workspace, a question came up on why Usage Meter 3.6.1 (UM) was failing to connect to a newly deploy vRealize Operations (vROps) 8.1 instance.
The failure message that was being received was “incorrect username or password”, even though the credentials were correct. Firewall rules were not blocking accessibility.
In my lab environment, I had vROps 8.0 working successfully –
I upgraded my vROps instance, and attempted to recreate this issue.
I started to receive the following errors (please disregard the version detection, this seems to always be quirky) –
Changes in vROps Authentication
Starting with vROps 8.1, basic authentication via the API is disabled. Usage Meter 3.6.1 utilizes a local account for metering purposes and does this through the API. Therefore, one must re-enable basic authentication via the API.
The VMware Knowledge Base article depicts this scenario, but here are the steps required.
- Log into the vRealize Operations Manager Master node as root via SSH.
- Open /usr/lib/vmware-vcops/user/conf/api-conf.properties in VI.
- Change the basicAuthentication.enabled property value to true.
- Example: basicAuthentication.enabled=true
- Save and close the file.
- Restart the REST API service:
service api restart
- Repeat steps 1-5 on all other nodes in the vRealize Operations Manager cluster.
Finally, after applying the changes to my environment, vROps metering is now operational.