Hello, all. I read in a post from 2006 that 389 does not support referential integrity for memberuid. That would seem like a great inconvenience. Has that been changed or is it still impossible? Is there any chance of it changing? I suppose we are a little spoiled in our environment in that uids are globally unique. I can see how this could be a problem when there are non-unique uids but, since referential integrity can be configured to take specific attributes, I was hoping we could enforce it in our case :-( Thanks - John
