Ticket #1007 (closed defect: invalid)

Opened 3 years ago

Last modified 2 years ago

review the local domain min_id/max_id

Reported by: jhrozek Owned by: somebody
Priority: major Milestone: void
Component: Local Provider Version: 1.6.1
Keywords: Cc:
Blocked By: Blocking:
Tests Updated: no Coverity Bug:
Patch Submitted: no Red Hat Bugzilla: 741164
Design link:
Feature Milestone:
Design review: Fedora test page:
Chosen: Candidate to push out:
Release Notes:

Description

See: https://bugzilla.redhat.com/show_bug.cgi?id=741164

There are two issues:

1) the example config in the SSSD tree uses min_id and max_id. I don't think it should, the code enforces a different min_id value for local domain and "regular" domains.

2) now that shadow-utils defaults to min_id of 1000, we might consider bumping up the local default to something bigger to avoid immediate clashes with shadow users.

Change History

comment:1 Changed 3 years ago by sgallagh

1) Yes, the example config has several entries in it that are no longer correct. We should open another ticket to go through and update it completely.

2) Frankly, defaulting to 1000 was probably never a good idea to begin with. Perhaps we should start with 20000 to be absolutely certain?

comment:2 Changed 3 years ago by jhrozek

  • Resolution set to invalid
  • Status changed from new to closed

As agreed on today's team meeting, we will not bump up the default. The issue in the BZ linked is primarily a configuration issue due to our incorrect example config file. I have filed https://fedorahosted.org/sssd/ticket/1014 to track the config file improvements.

This bug can be closed now.

comment:3 Changed 2 years ago by mkosek

  • Red Hat Bugzilla changed from 741164 to [https://bugzilla.redhat.com/show_bug.cgi?id=741164 741164]

comment:4 Changed 2 years ago by simo

  • Milestone changed from NEEDS_TRIAGE to void
Note: See TracTickets for help on using tickets.