What | Removed | Added |
---|---|---|
Resolution | --- | FIXED |
Status | NEW | RESOLVED |
So reading between all the lines here, no one actually reported what the real issue was, and that issue was that users defined by sysusers also imply a group. The 389 config was *correctly* adding a group and user, since there was no obvious communication that the group is implied. This has already been fixed via obs.