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.

Starting in the development environment we've started noticing the dynflow console /foreman_tasks/dynflow no longer allows the admin user to access it when logged in.  Attempts to access it result in 'Forbidden' 

Logging out and logging back in does not seem to help.

Flipping the dynflow_console_require_auth setting to 'No' seems to allow the user to access the dynflow console.

I'm currently seeing this running foreman-tasks 0.8.24 with foreman 3cf5b75af76d69fc6db869a44654db1d3133c665

Created from redmine issue http://projects.theforeman.org/issues/20036

Upstream bug assigned to aruzicka

This issue prevents users to access dynflow console: definitely a blocker for next release

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

Verified in Sat 6.3 snap 12, admin user can now access dynflow as expected

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, 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-2018:0336

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, 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-2018:0336