#167 sss_tools should not invoke shadow-utils tools
Closed: Fixed None Opened 13 years ago by sgallagh.

Related to Bug 165, we are not going to support using the sss_* tools to create users anywhere but in the provider=local domain.

Determining when to invoke the shadow-utils is causing far too many edge cases to handle, and with the removal of formal support for the "LEGACYLOCAL" migration domain (Bug 165), supporting it is meaningless.

We should treat it like any other information source such as LDAP: it should continue to be managed with the tools designed specifically for its use.

Fixed with 7a9bee0

fixedin: => 0.6.0
resolution: => fixed
status: new => closed

Fields changed

tests: 1 => 0
testsupdated: 0 => 1

What's the extent of the "affects doc" tag here? Is it just a case of updating the man pages to read "<do something> in the local domain" instead of just "<do something>"? e.g., creating a new group with sss_groupadd can only add a group to the local domain. I'm assuming of course that this goes beyond creating users.


Before we made this change, the sss_* tools would try to manage users and groups in the internal SSSD domain if it belonged there, otherwise it would internally invoke the traditional shadow-utils tools and operate on /etc/passwd and /etc/group.

As of this patch, we no longer do that (we agreed that it was potentially dangerous to manipulate features we don't own)

So if the docs referred to this implicit invocation of shadow-utils, it needed to be updated. If it does not, then you need take no action.

Fields changed

docupdated: 0 => 1

Fields changed

rhbz: => 0

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

5 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/1209

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.