Bug 614495

Summary: API does not show user enabled/disabled status
Product: [Retired] Red Hat Network Reporter: Guil Barros <gbarros>
Component: RHN/APIAssignee: Stephen Herr <sherr>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Network Quality Assurance <rhn-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: RHN StableCC: acarter, ggainey
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-02 20:53:42 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: 613121    
Attachments:
Description Flags
Test script showing existence of 'disabled' flag in user.getDetails(token) none

Description Guil Barros 2010-07-14 15:27:23 UTC 
The current RHN API does not allow us to query if a user is enabled or disabled. This feature is currently available in the Satellite API.
Comment 1 Grant Gainey 2010-07-15 14:45:28 UTC 
Modifying user.getDetails(token) to return this info:

=====
 Method: getDetails
Description:
Returns the details about a given user.

Parameters:

    * string sessionKey
    * string login - user sought

Returns:

    * struct (user details)
          o string "first_names"
          o string "last_name"
          o string "email"
          o string "prefix"
          o string "last_login_date"
          o string "created_date"
          o string "disabled" - 'true'/'false', is this user disabled?
=====

commit 886e182c6f72775eeab0fb115e77dba4dc067eb6
Comment 2 Grant Gainey 2010-07-15 14:46:09 UTC 
Created attachment 432104 [details]
Test script showing existence of 'disabled' flag in user.getDetails(token)