Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1546718 - AD users(SSO) not able to authenticate API calls
Summary: AD users(SSO) not able to authenticate API calls
Keywords:
Status: CLOSED DUPLICATE of bug 1266407
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.2.13
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-19 12:05 UTC by Suraj Patil
Modified: 2018-02-20 18:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-20 18:36:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Suraj Patil 2018-02-19 12:05:28 UTC 
Description of problem:
AD users are not able to authenticate API calls.

When AD is integrated with the satellite using AD direct method (SSO) API calls does not authenticate. 
If the AD is integrated with satellite web UI (LDAP way) API call works.


How reproducible:

Setup an AD direct server according to administration guide chapter 8.3.2
and then try to make an API call using AD user. 


Actual results:
Failed to authenticate.

Expected results:
Should authenticate and show the results.


Additional info:
This is similar bug as 1266407
Comment 1 Brad Buckingham 2018-02-20 18:36:15 UTC 
Based on feedback in core triage, this is a duplicate of bug 1266407, referenced in the description.  Please feel free to re-open with additional details, if there are concerns.

*** This bug has been marked as a duplicate of bug 1266407 ***
Note You need to log in before you can comment on or make changes to this bug.