WorkspaceSchemaGroupAttributes
{
"distinguishedName": "CN=all-admin-users,CN=Users,DC=acme,DC=com",
"internalGroupType": "EXTERNAL",
"domain": "acme.com",
"description": "The group for all admin users",
"compositionRules": "{\n \"addedUserIds\" : [ ],\n \"excludedUserIds\" : [ ],\n \"rule\" : {\n \"type\" : \"internalGroup\",\n \"groupId\" : \"53cc45f9-2e21-4fa4-ae81-32e6fb15bd91\"\n }\n}",
"userStoreUuid": "acme.com",
"parents": [
{
"operation": "string",
"type": "string",
"primary": false,
"value": "string",
"display": "string"
}
],
"compositionRulesV2": false,
"email": "all-admin-users@acme.com"
}
The group distinguished name if available
The internal group type. Available values are: 'EXTERNAL' (when the group comes from an external source), DYNAMIC (local group with custom rules), INTERNAL (local group with static rules), ALL_USERS (the default group containing all users)
The group domain: can be the domain coming from an external source as AD or a local domain like 'System Domain'
The group description if available
The group composition rules version 1. Those rules are populated with relevant information when a dynamic group is created.
The group user store identifier (userStoreUuid) if available. This is deprecated and will be replaced soon by the directory identifier
The list of group parents if available. The groups can be nested and VMware Identity Manager will return the full hierarchy
The group composition rules version 2. Those rules are populated with relevant information when a dynamic group is created.It adds support for user uuid and group uuid
The group email if available