InlineTokenBasedPrincipalIdentity1

JSON Example

{
    "is_protected": false,
    "name": "string",
    "node_id": "string",
    "roles_for_paths": [
        {
            "delete_path": false,
            "path": "string",
            "roles": [
                {
                    "role": "string",
                    "role_display_name": "string"
                }
            ]
        }
    ]
}

boolean

is_protected

Optional

Indicator whether the entities created by this principal should be protected.

string As /^[a-zA-Z0-9]+([-._@]?[a-zA-Z0-9]+)*$/

name

Required

Constraints: maxLength: 255

Name of the principal. This will be matched to the name provided in the token.

string As /^[a-zA-Z0-9]+([-._]?[a-zA-Z0-9]+)*$/

node_id

Required

Constraints: maxLength: 255

Unique node-id of a principal. This is used primarily in the case where a cluster of nodes is used to make calls to the NSX Manager and the same 'name' is used so that the nodes can access and modify the same data while still accessing NSX through their individual secret (certificate or JWT). In all other cases this can be any string.

array of RolesForPath

roles_for_paths

Optional

The roles that are associated with this PI, limiting them to a path. In case the path is '/', the roles apply everywhere.

Used By

TokenBasedPrincipalIdentity