Bug 1463690

Summary:	dynflow console doesn't seem to honor authentication
Product:	Red Hat Satellite	Reporter:	Ivan Necas <inecas>
Component:	Tasks Plugin	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3.0	CC:	aruzicka, ehelms, inecas, jcallaha
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman-tasks-0.9.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:51:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ivan Necas 2017-06-21 13:57:34 UTC

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

Comment 1 Ivan Necas 2017-06-21 13:57:39 UTC

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

Comment 2 Ivan Necas 2017-06-21 13:57:45 UTC

Upstream bug assigned to aruzicka

Comment 4 Ivan Necas 2017-06-21 14:10:30 UTC

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

Comment 5 Satellite Program 2017-06-21 14:11:52 UTC

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

Comment 6 Peter Ondrejka 2017-08-23 11:22:00 UTC

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

Comment 7 Bryan Kearney 2018-02-21 16:45:23 UTC

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

Comment 8 Satellite Program 2018-02-21 16:51:07 UTC

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