Tenant Tenant Manager Mark Service Provider Entities
Define a set of ManagedEntity objects as used for tenant management.
Those entities are a starting point of an inventory hierarchy (sub-tree) that functionally exists in the tenant's inventory but are owned by the system user of the vCenter Server. The operations which the tenant may perform on these objects depend on the permissions granted to the tenant by the SaaS provisioning layer. Permissions that the tenant may create on the parent objects of the management entities do not propagate to the hierarchies of management entities and thus have no effect on them. This operation will fail for all the entities if any of them does not exist. The method behaviour is transactional - either all entities are marked or none if an error occurs while processing them. The user calling this method should hold TenantManager.Update on the root folder and TenantManager.Update on each entity currently being marked as a service provider one. These are strict privilege requirements allowing only administrators to call the method.
Required privileges: TenantManager.Update
The unique identifier for the managed object to which the method attaches; the serialized managed object reference for a request has the form moType/moId
, in this case TenantTenantManager/{moId}
.
The vSphere release schema. The current specification covers vSphere 8.0.2.0 APIs.
{
"entity": [
{
"_typeName": "string",
"type": "string",
"value": "string"
}
]
}
an array of management entities.
Required privileges: TenantManager.Update
No Content
ManagedObjectNotFound: if any of the entities doesn't exist.
AuthMinimumAdminPermission: if this change will leave the system with no Administrator permission on the root folder of the service provider inventory.
{
"_typeName": "string",
"faultCause": "MethodFault Object",
"faultMessage": [
{
"_typeName": "string",
"key": "string",
"arg": [
{
"_typeName": "string",
"key": "string",
"value": {
"_typeName": "string"
}
}
],
"message": "string"
}
]
}
The base data object type for all the object model faults that an application might handle.
Message which has details about the error Message can also contain a key to message catalog which can be used to generate better localized messages.