#112 provider = files adding a group or user without defining a uidNumber or gidNumber result in error
Closed: Invalid None Opened 14 years ago by jgalipea.

Description:
When adding a user or group without defining a uidNumber/gidNumber, it results in "Cannot get domain info". [[BR]] [[BR]]

With a Range defined:[[BR]]
I would expect a better error message such as "UID/GID is required" or even "The selected UID/GID is outside all domain ranges"[[BR]] [[BR]]

With a Range undefined: [[BR]]
I would expect the user or group to be added successfully with the next available ID number. Just like the shadow utils. [[BR]] [[BR]]

Version Tested:
sssd-2009081709-0.fc11.i586


This bug is present when attempting to run the sss_tools against an SSSD configuration with no provider=local domain configured.

We are currently debating whether to remove the ability to add a legacy user or group with the sss_tools. If we decide to do this, the error message will be changed to reflect that no local domain can be found.

If we decide to leave the legacy add/remove support in place, we will change the initialization code here to reflect that a provider=files domain is permissible.

component: SSSD => sss_tools
milestone: SSSD 1.0 => Iteration 7
owner: somebody => jhrozek

Fields changed

status: new => assigned

As per #167 we are removing the functionality altogether. Fix was present in patchset sent for review, must remove it in next iteration.

doc: => 0
docupdated: => 0
resolution: => wontfix
status: assigned => closed
tests: => 0
testsupdated: => 0

Metadata Update from @jgalipea:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 0.6.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/1154

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