Bug 172513 - The 'user.delete' api call should be replaced with/supplemented by calls for enabling and disabling a user
The 'user.delete' api call should be replaced with/supplemented by calls for ...
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Jesus M. Rodriguez
Brandon Perkins
Depends On:
Blocks: 169463
  Show dependency treegraph
Reported: 2005-11-05 14:16 EST by Robin Norwood
Modified: 2007-06-20 14:09 EDT (History)
1 user (show)

See Also:
Fixed In Version: rhn410
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-19 14:49:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robin Norwood 2005-11-05 14:16:21 EST
User deletion in hosted almost never works.  We should allow user
disabling/enabling via the API instead.
Comment 1 Michael Bowman 2005-11-08 10:56:52 EST
User deletion is not allowed in hosted. It should *never* work ;)

Added disable/enable functionality to the api. This works in both hosted and

Test plan
- Make sure you cannot delete users via the api in hosted
- Make sure you can delete users via the api in satellite
- Make sure you can enable/disable users in both environments. You should check
for the same functionality and use cases through the api as we have through the
web-ui; i.e., org admin -> normal user, org admin -> org admin, org admin ->
self, org admin -> self when last in org, etc..

Comment 2 Brandon Perkins 2006-06-28 13:12:29 EDT
Not sure how this slipped through the cracks...but it should be aligned with 410.
Comment 3 Brandon Perkins 2006-06-28 13:14:19 EDT
Looks like this should have been on QA since 2005-11-08.
Comment 4 Brandon Perkins 2006-06-28 13:16:28 EDT
Verified.  Test code at:

Comment 5 Beth Nackashi 2006-07-19 14:49:58 EDT
moving to closed - currentrelease

Note You need to log in before you can comment on or make changes to this bug.