Bug 13004 - objectSID can be not-unique in AD due to conflict resolution
objectSID can be not-unique in AD due to conflict resolution
Status: NEW
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB
4.7.0rc5
All All
: P5 normal
: ---
Assigned To: Andrew Bartlett
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-31 03:55 UTC by Andrew Bartlett
Modified: 2017-08-31 04:09 UTC (History)
1 user (show)

See Also:


Attachments
a possible solution (569 bytes, patch)
2017-08-31 03:55 UTC, Andrew Bartlett
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Bartlett 2017-08-31 03:55:45 UTC
Created attachment 13522 [details]
a possible solution

If there is conflict resolution on a foreignSecurityPrincipal that can cause a unique index constraint on objectSID, as both the original and conflict object exist at the same time.  Deleting the conflict object doesn't help, as the deleted object is still in the index.