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.

Description of problem:
Admin needs to change the setting oidc_audience value each time a user uses different client id.

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


Steps to Reproduce:
1. Create 2 clients on RHSSO, one for hammer and other for Satellite
2. Try to login from both the platforms

Actual results:
Admin is being able to provide just one audiance right now.

Expected results:
Admin must be able to provide all the client ids involved inside Satellite settings.

Upstream bug assigned to rabajaj

Upstream bug assigned to rabajaj

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29386 has been resolved.

'oidc_audience' settings now contain the list, after applying both audiences specific to UI and Hammer, I was able to login using the hammer (two factors) mentioned steps are here https://access.redhat.com/documentation/en-us/red_hat_satellite/6.7/html/administering_red_hat_satellite/chap-red_hat_satellite-administering_red_hat_satellite-configuring_external_authentication#integrating-satellite-with-red-hat-single-sign-on-for-external-authentication. Verified with Satellite 6.8 Snap1.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366