Project

General

Profile

Actions

Bug #20036

closed

dynflow console doesn't seem to honor authentication

Added by Justin Sherrill over 7 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman plugin
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

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

Actions #1

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Adam Ruzicka
  • Pull request https://github.com/theforeman/foreman-tasks/pull/259 added
Actions #2

Updated by Adam Ruzicka over 7 years ago

  • Category set to Foreman plugin
  • Target version set to 1.14.1
Actions #3

Updated by Ivan Necas over 7 years ago

  • Translation missing: en.field_release set to 261
Actions #4

Updated by Adam Ruzicka over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #5

Updated by Ivan Necas over 7 years ago

  • Bugzilla link set to 1463690
Actions

Also available in: Atom PDF