Skip to content
English
  • There are no suggestions because the search field is empty.

Discovery fails with "Unable to authenticate with REST api"

Why VMware discoveries fail with "Unable to authenticate with REST api" for a standalone ESXi host or a vCenter that refuses the REST logon, and how to fix it.

Applies to: Opslogix VMware Management Pack (all versions) · SCOM 2019, 2022, 2025 · vCenter and ESXi 7.0, 8.0, 9.0
Last updated: November 2026 · Reading time: 4 minutes

Symptoms

New ESXi hosts, datastores or virtual machines aren't discovered, and changes to existing ones don't show up in SCOM. The Operations Manager event log on the management servers of the VMware resource pool shows warnings like this, for the DISCOVERY:GENERIC and DISCOVERY:VIRTUALMACHINE workflows:

There was a problem running workflow 'DISCOVERY:GENERIC' for connection https://<host>/sdk
... detail=Unable to authenticate with REST api. url=https://<host>:443/api/session

Cause

The discoveries read most data through the vSphere Web Services API (/sdk). The vSphere tags of hosts and virtual machines come from a different API: the vCenter REST API (/api). When the logon to the REST API fails, versions before 26.11.4549.0 stop the whole discovery, even though the rest of the data is available. This happens in two situations:

  • The connection is a standalone ESXi host, added directly instead of through vCenter. ESXi has no tagging API, so the logon always fails.
  • The connection is a vCenter server whose REST API refuses the monitoring account, while the vSphere Web Services API accepts it.

In versions before 26.11.4549.0, turning off tag discovery doesn't help: the discovery still logs on to the REST API.

Solution

Upgrade to version 26.11.4549.0 or later. The discovery then no longer depends on the REST API:

  • Standalone ESXi host: the tags are skipped, and the host, its datastores and its virtual machines are discovered. See Monitor a standalone ESXi host (without vCenter).
  • vCenter: the objects are discovered without tags, and the collector logs one of these warnings instead:
    • Unable to retrieve tags for default object discovery, Skipping tags.
    • Unable to retrieve tags for virtualmachines, Skipping tags.

For a vCenter, also fix the REST logon. Tags and the VMware Appliance Monitoring management pack both need it:

  1. On a management server of the VMware resource pool, test the logon with the monitoring account. curl.exe asks for the password:
    curl.exe -k -u "<monitoring account>" -X POST https://<vcenter>/api/session
    A session ID in quotes means the logon works. An error with UNAUTHENTICATED means vCenter refuses the account. -k skips the certificate check; leave it out if the server trusts the vCenter certificate.
  2. If the logon is refused, check the account in vCenter: that it isn't locked or expired, and that the password in the connection is current. See Set up a VMware monitoring account.
  3. If you use appliance monitoring, see VCSA appliance monitoring fails with an access error.

If you don't use vSphere tags in SCOM, you can also turn tag discovery off. From version 26.11.4549.0, the discovery then doesn't log on to the REST API for tags at all. See Disable Tags discovery in the VMware MP.

Verify it worked

Discovery runs on a schedule, so it can take several hours before missing objects appear. After the next discovery of the connection, the event log no longer shows Unable to authenticate with REST api for the discovery workflows, and the missing objects appear in SCOM.

See also