7.4

Table Of Contents
Table 118. Custom Properties for Networking Configuration (Continued)
Custom Property Description
VCNS.SecurityTag.Names.name Specifies the NSX security tag or tags to which the virtual
machine is associated during provisioning. The value is a
security tag name or a list of names separated by commas.
Names are case-sensitive.
Appending a name allows you to create multiple versions of the
property, which can be used separately or in combination. For
example, the following properties can list security tags intended
for general use, for the sales force, and for support:
n
VCNS.SecurityTag.Names
n
VCNS.SecurityTag.Names.sales
n
VCNS.SecurityTag.Names.support
VMware.Endpoint.NSX.HideDiscoveredSecurityObjects
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. 44