Bug 1316297

Summary: Various API functions related to users and Auth Sources do not work
Product: Red Hat Satellite Reporter: Stephen Clayton <sclayton>
Component: APIAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.7CC: bkearney, mmccune, sclayton
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-09 23:04:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Stephen Clayton 2016-03-09 22:14:29 UTC 
Description of problem:

GET /api/usergroups/[ID]/external_usergroups
GET /api/auth_source_ldaps/[ID]/external_usergroups

Accessing either of these URLs with the required ID yields an error message:

“The page you were looking for doesn’t exist. You may have mistyped the address or the page may have moved."

Version-Release number of selected component (if applicable):


How reproducible:

Consistently reproducible

Steps to Reproduce:

While authenticated to a Satellite 6 server, in your browser go to the following URLs, replacing [ID] with the corresponding ID of a user group or auth source.

https://[SATHOST]/api/usergroups/[ID]/external_usergroups
https://[SATHOST]/api/auth_source_ldaps/[ID]/external_usergroups

Actual results:

“The page you were looking for doesn’t exist. You may have mistyped the address or the page may have moved."

Expected results:

JSON formatted list of external usergroups and their mappings.

Additional info:
Comment 1 Stephen Clayton 2016-03-09 22:57:55 UTC 
These also do not work, in a similar fashion....

/api/auth_source_ldaps/:auth_source_ldap_id/users
/api/usergroups/:usergroup_id/users
/api/roles/:role_id/users
/api/locations/:location_id/users
/api/organizations/:organization_id/users
Comment 2 Stephen Clayton 2016-03-09 23:04:47 UTC 
It looks like I have to manually specify using version 2 of the API. That fixes the issue as far as I can tell...

It might help to VISUALLY emphasize this in the API documentation