7.4

Table 1‑45. Custom Properties V Table (Continued)
Property Description
VMware.Endpoint.Openstack.IdentityProvider.Dom
ain.Name
Allows vRealize Automation to support required Keystone V3 domain-
name authentication. If Keystone V3 is in effect, you can use the
property to designate a specific domain for the OpenStack endpoint to
authenticate with a Keystone V3 OpenStack identity provider.
n
For new endpoints, add the custom property to designate a
specific domain.
n
For upgraded or migrated endpoints, add the custom property only
if data collection fails after upgrade or migration.
VMware.Endpoint.Openstack.IdentityProvider.Ver
sion
Specifies the version of OpenStack identity provider (Keystone) to use
when authenticating an OpenStack endpoint. Configure a value of 3 to
authenticate with Keystone V3 OpenStack identity provider. If you use
any other value, or do not use this custom property, authentication
defaults to Keystone V2.
VMware.Endpoint.Openstack.Release
Deprecated. Specifies the OpenStack release, for example Havana or
Icehouse, when creating an OpenStack endpoint. Required for 6.2.1,
6.2.2, and 6.2.3 OpenStack provisioning.
VMware.Endpoint.NSX.HideDiscoveredSecurityObje
cts
Set to true to hide newly discovered security objects in the active
tenant for the NSX endpoints to which the security objects are
associated. Otherwise, all new security objects are available to all
tenants after data collection, provided that the security object is for an
endpoint in which you have a reservation. This option allows you to
prevent users from accessing security objects when you want to
assign those objects to a single tenant or to mask from all tenants. Set
to false to toggle back to global, which enables all new security objects
to be available to all tenants after data collection, provided that the
security object is for an endpoint in which you have a reservation.
To take effect, the fabric administrator adds the
VMware.Endpoint.NSX.HideDiscoveredSecurityObjects custom
property to the associated NSX endpoint that is associated to a
vSphere endpoint. The setting applies to the next inventory data
collection. Existing security objects remain unchanged.
To change the tenancy setting of a security object that has already
been data-collected, such as existing security objects after upgrading
to the current vRealize Automation release, you can edit the security
object’s Tenant ID setting programmatically by using the
vRealize Automation REST API or vRealize CloudClient. The available
Tenant ID settings for the NSX endpoint are as follows:
n
"<global>" - the security object is available to all tenants. This is
the default setting for existing security objects after upgrade to this
release and for all new security objects that you create.
n
"<unscoped>" - the security object is not available to any tenants.
Only the system administrator can access the security object. This
is an ideal setting when defining security objects that are to
eventually be assigned to a specific tenant.
n
"tenant_id_name" - the security object is only available to a
single, named tenant.
Custom Properties Reference
VMware, Inc. 93