Horizon doesn't obtain domain scoped tokens for users coming through websso

Bug #1655560 reported by Radu Pasea
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Triaged
Medium
Unassigned

Bug Description

We have a Mitaka deployment in which users can login using an external SSO service and the Keystone external authentication protocol and are mapped to a Keytone domain. Domain admin users from that domain can't perform any admin operations in the frontend because Horizon doesn't obtain a domain scoped token.

With external authentication, Keystone tokens always have the user domain present, so this shouldn't be an issue in Horizon.

In my opinion, the bug is in the django_openstack_auth project. Here, on the websso path, I think the user domain is expected to be provided by the user in the login page, which, of course, isn't possible for websso.

As a solution, the unscoped Keystone token can be checked for the user domain.

I have attached a patch for the 2.2.1 tag of django_openstack_auth. Seeing code here hasn't been modified in a long time, the bug should manifest itself in the newest version of Horizon.

Tags: keystone
Revision history for this message
Radu Pasea (rpasea) wrote :
description: updated
tags: added: keystone
removed: dashboard-core
Changed in horizon:
status: New → Triaged
importance: Undecided → Medium
milestone: none → next
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.