Bug 638658

Summary: [RFE] - Change Satellite API call users.listUsers
Product: Red Hat Satellite 5 Reporter: Chris Williams <cww>
Component: APIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 530CC: acarter, cperry
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 638645 Environment:
Last Closed: 2010-10-07 08:49:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 628012    

Description Chris Williams 2010-09-29 15:30:55 UTC
+++ This bug was initially created as a clone of Bug #638645 +++

1. Customer Name: Comcast 
2. What is the nature and description of the request? Enhancement to RHN API users.listUsers 
3. Why does the customer need this? (List the business requirements here): Easier management of RHN accounts. 
4. How would the customer like to achieve this? (List the functional requirements here): Currently users.listUsers does not provide any indication if an account is disabled or not. Customer would like it to either not list disabled users, or, include a field indicating 'disabled'. 
5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Invoke users.listUsers against an RHN account that has disabled users associated with it. Verify that it either does not list the disabled users, or that it indicates which users are disabled. 
6. Is there already an existing RFE upstream or in Red Hat bugzilla? Not that I was able to find. 
7. How quickly does this need resolved? (desired target release) Customer would like to have this asap, though I wouldn't consider it critical. Next major release? 
8. Does this request meet the RHEL Inclusion criteria (please review) Not RHEL. If we get this in RHN Satellite, would it also get into RHN hosted? 
9. List the affected packages RHN, RHN Satellite

Comment 2 Tomas Lestach 2010-10-07 08:49:11 UTC
One BZ per issue has always been enough.

*** This bug has been marked as a duplicate of bug 638645 ***