I have the following setup on my laptop. I have a local (traditional files) user with UID 500.
I created an SSSD domain called LOCAL with the UID range 500-999. I stopped SSSD, deleted the sssd.ldb file (to ensure a clean state) and then started it again.
I ran sss_useradd sss_user. Because there was no NextID entry in the sssd.ldb, it created the sss_user with UID 500.
Before finalizing on a UID, the SSSD should verify that there are no other users with that UID on the system, provided by other identity sources. (E.g., a getpwuid command should be run, or an equivalent function to avoid loops in SSSD).
Fields changed
status: new => assigned
priority: major => critical
This is a serious issue that should be addressed by 0.5.0
priority: critical => blocker
Reassigning to myself.
component: SSSD => sss_tools milestone: SSSD 1.0 => Iteration 6 owner: jhrozek => sgallagh status: assigned => new
This is not an issue that the SSSD is intended to solve. We will document this limitation.
This was a misconfiguration from the perspective of the SSSD. Failing to have a sensible domain range caused this problem.
fixedin: => Doc resolution: => wontfix status: new => closed
This also was occurring with groups. Example with magicPrivateGroups = TRUE: add a group with gid 1000 add a user with uid 1000 user's MPG is created with gid 1000 (non-unique gid)
Metadata Update from @sgallagh: - Issue assigned to sgallagh - Issue set to the milestone: SSSD 0.5.0
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/1099
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.