#119 sss_useradd shouldn't reuse UIDs/GIDs when creating local users
Closed: Fixed None Opened 14 years ago by sgallagh.

Steps to reproduce:

  1. Create a native local domain with no maxID
  2. Create a user without specifying the userid

    sss_useradd user1000

  3. Note {{{user1000}}}'s UID (e.g. 1000).

  4. Verify that the following command indicates that the nextId = 1001

    ldbsearch -H /var/lib/sss/db/sssd.ldb 'nextid=*'

  5. Create a user with the nextId specified explicitly

    sss_useradd -u 1001 user1001

  6. Verify that {{{user1001}}}'s UID is 1001

  7. Create another user without specifying the ID

    sss_useradd user1002

Expected behavior:
user1002 has UID 1002 and nextID is set to 1003

Actual behavior
user1002 is given UID 1001 (already in use by user1001) and nextID is set to 1002

While the use of the -u option is discouraged, it is still supported. We should ensure that our autonumbering system takes these users into account.


Fields changed

status: new => assigned

Fixed in b776f0a

fixedin: => 0.5.0
resolution: => fixed
status: assigned => closed

Fields changed

doc: => 0
docupdated: => 0
tests: => 0
testsupdated: => 1

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 0.5.0

7 years ago

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/1161

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata