This document serves as a troubleshooting reference for administrators managing Attribute-Based Access Control (ABAC).
I accidentally removed all users from a room after setting a room attribute. What should I do?
If users were unintentionally removed from a room after updating a room attribute, the attribute configuration may be incorrect.
Resolution:
Remove the incorrect attribute from the room or update it with the correct value.
Re-invite users to the room using the
/v1/groups.inviteAPI endpoint.
Why isn’t a user attribute appearing in Admin → Users → User Info?
Missing user attributes are typically caused by mapping or synchronization issues.
Resolution:
Verify that attribute mappings are correctly configured in LDAP.
Check whether the background synchronization process is running successfully.
Trigger a manual synchronization by calling the
/v1/abac/users/syncendpoint to force an attribute update.
A user was unexpectedly removed from a room after I changed a room attribute. Why did this happen?
This usually occurs when there is a mismatch between LDAP attribute mappings and the room configuration.
Resolution:
Confirm that LDAP mappings are properly configured. Remember that attribute values are case-sensitive.
In Admin → Users → User Info, verify that the capitalization and spelling of both user and room attributes match exactly.