Previously, the value of the custom group domain could be an arbitrary string, normally the name of the tenant was being used as a value.
In the case when a new custom group was being created, an API request similar to the following had to be issued:
POST /api/tenants/{tenantId}/groups
{"groupType":"CUSTOM", "name":"arbitrary-group-name", "description":"arbitrary-group-description", "principalId":{"domain":"arbitrary-group-domain", "name":"arbitrary-group-name"}}
In vRA 7.4, when creating a custom group, the value of the custom group domain must always be set to the system domain configured in vRealize Automation (normally, vsphere.local).
For example:
POST /api/tenants/{tenantId}/groups
{"groupType":"CUSTOM", "name":"arbitrary-group-name", "description":"arbitrary-group-description", "principalId":{"domain":"vsphere.local", "name":"arbitrary-group-name"}}
For other API operations like in the case when retrieving a custom group, it must be referred to with the system domain configured in vRealize Automation (normally, vsphere.local).
For example:
GET /identity/api/tenants/{tenantId}/groups/[email protected]