Symptoms:
VMware vCenter Server 7.x
VMware vCenter Server 8.x
This issue typically occurs due to one of two primary architectural causes:
Missing Global Permissions (RBAC Architecture):
In vSphere, the direct parent of Content Libraries is the Global Root object rather than the standard vCenter Server inventory tree (Datacenter, Cluster, VM, Datastore). Privileges assigned at the vCenter Server or Datacenter levels propagate downward through compute and storage containers, but do not propagate horizontally or upward to the Content Library service daemon (cls).
Without an explicit Global Permission, the service token check fails, causing the catalog query to return zero items.
Missing Datastore / Storage Privileges:
Even with Content Library visibility, enumerating and mounting raw media requires explicit read access (Datastore.Browse) on the specific datastore backing the library.
Compute-to-Storage Identifier Mismatch:
In certain multi-host or shared-storage configurations, internal datastore Managed Object Reference (MoRef) IDs evaluated between the ESXi host compute resource and the Content Library service filter out accessible media, causing the vSphere Client to suppress the item list.
To resolve the issue:
Configure RBAC via Global Permissions (Mandatory for Custom Roles)
To allow users to view and mount Content Library ISOs without exposing unneeded infrastructure:
1. Create a Dedicated Content Library Role:
2. In the vSphere Client, navigate to Administration > Access Control > Roles.
3.Click New and create a scoped role (e.g., Content-Library-Consumer) containing only the following privileges:
a. Content library > Read storage
b. Content library > Download session
c. Content library > View configuration
d. Content library > Probe storage
Note: Do not add general vCenter, host, or VM administration privileges to this role.
4. Assign the Role Under Global Permissions:
a. Navigate to Administration > Access Control > Global Permissions.
b. Click Add (+), select the target user or group, assign the custom Content-Library-Consumer role, and check Propagate to children.
Note: Because this role contains no compute, VM, or host privileges, it grants access to the Content Library API without exposing other vCenter inventory objects.
5. Assign Object-Level Permissions:
a. Backing Datastore: Navigate to Storage view > select the backing datastore > Permissions tab > grant the user/group a role containing Datastore > Browse datastore.
b. Target Virtual Machine: Select the VM (or VM folder) > Permissions tab > grant the user/group permissions containing:
c. Virtual machine > Change configuration > Modify device settings
d. Virtual machine > Interaction > Connect devices
6. Refresh Session Tokens:
vSphere Client caches SSO authorization tokens. Have the user log out completely and log back in (or use an Incognito/Private browser window).
Broadcom Documentation: Content Library Privileges in vSphere 8.0
"The direct parent for content libraries is the global root. This relationship means that if you set a permission at a vCenter Server level and propagate it to the children objects, the permission applies to data centers, folders, clusters, hosts, virtual machines, and so on, but does not apply to the content libraries... To assign a permission on a content library, an Administrator must grant the permission to the user as a global permission."
VMware Aria Automation Documentation: Permissions on Content Libraries