Currently, this scenario will fail because crowd will attempt to add a row with a duplicate primary key to the membership database table.
JIRA attempts to apply group memberships when synchronising from a remote directory even if they already exist, causing a duplicate key violation
If a user exists in two directories in an application, and is added to a group in one directory that it was already in the other, clients get duplicate key errors
Failing incremental Crowd/Crowd synchronisation should fall back to full synchronisation
Incremental Crowd/Crowd synchronisation produces inconsistent events when a membership is deleted and recreated