Synchronizing users and groups
Event-triggered synchronization
Trigger event | Synchronization |
---|---|
When the server starts in the pod. |
All available groups are synchronized with the Business Automation Workflow database, so that all external groups are available for Business Automation Workflow modeling and execution. During this startup synchronization, if a previously synchronized external group is not present, then its absence is noted in the database by setting a deleted flag, but the group is not removed from the database. This startup synchronization does not update any group membership information. |
When a user is searched for. For example:
|
All users that are found during the search are created in the Business Automation Workflow database, even if they are not added to the group or team. |
During user authorization. For example:
|
If the user doesn't exist in the Business Automation Workflow database, the user is created in the database and the user information is synchronized with the user registry information (full name and distinguished name). The groups that the user belongs to in the user registry are synchronized to ensure that the Business Automation Workflow database content reflects the current state of the user registry for the user. If the is a member of one or more groups that were not previously synchronized, these groups are now created in the Business Automation Workflow database, too. Only the membership of this user in these new groups is reflected, the membership of other members of these newly added groups is not reflected until those other users log in. If a user was previously deactivated, the login reactivates the user in the Business Automation Workflow database. |
POST /system/users_sync
and POST
/system/groups_sync
.