Lists the ABAC attributes and values the caller can assign, sorted by key. ABAC must be enabled.
- Without
rid, the list covers a new ABAC-managed private room or team. Permission required:create-abac-managed-room. - With
rid, the list covers the attributes of that existing room. Permissions required:abac-managementandmanage-abac-admin-rooms, oredit-room-abac-attributesin that room.
With the local attribute store, the list contains every attribute definition. When Restrict room creators and editors to attributes they hold is on, it is limited to the values the caller holds plus, with rid, the values the room already has. ABAC administrators editing an existing room and users with bypass-abac-store-validation are not limited. With an external attribute store such as Virtru, the list contains the caller's entitlements.
requiredKeys lists the attribute keys every ABAC room must carry while Enforce ABAC across all workspace rooms is on. It is empty otherwise.
Changelog
| Version | Description |
|---|---|
| 9.0.0 | Added |
The authToken of the authenticated user.
The userId of the authenticated user.
Optional. The ID of an existing room. Include it to list the attributes you can assign to that room. Omit it to list the attributes you can assign when creating a room.
OK
{
"attributes": [
{
"key": "clearance",
"values": [
"confidential",
"secret"
]
},
{
"key": "department",
"values": [
"engineering"
]
}
],
"requiredKeys": [
"clearance"
],
"success": true
}Bad Request
{
"success": false,
"error": "error-abac-not-enabled",
"errorType": "error-abac-not-enabled"
}Present only when a specific attribute or cause is at fault.
Unauthorized
{
"success": false,
"error": "You must be logged in to do this."
}Forbidden
{
"success": false,
"error": "User does not have the permissions required for this action [error-unauthorized]"
}