Bug 1316297 - Various API functions related to users and Auth Sources do not work
Summary: Various API functions related to users and Auth Sources do not work
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.1.7
Hardware: All
OS: Linux
unspecified
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-09 22:14 UTC by Stephen Clayton
Modified: 2016-03-09 23:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-09 23:04:47 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


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