Since the existence of a domain token was equivalent with having
selected a domain context with Keystone V2, some code confuses the
two. This is no longer true for Kestone V3, so we have to separate
the two concepts and use domain context when we mean the domain
context.
Reviewed: https:/ /review. openstack. org/434193 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=df369b4c125 5ee89303fd82f4d a3388e8e480c07
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit df369b4c1255ee8 9303fd82f4da338 8e8e480c07
Author: Radomir Dopieralski <email address hidden>
Date: Wed Feb 1 15:23:34 2017 +0100
Disentangle domain context from effective domain
Since the existence of a domain token was equivalent with having
selected a domain context with Keystone V2, some code confuses the
two. This is no longer true for Kestone V3, so we have to separate
the two concepts and use domain context when we mean the domain
context.
Close-bug: #1661537
Change-Id: Ifa66d8c397e34d 16a4534e7216eb1 1c752699505 cb36988ce6dcd3f 5d0d96cf3b) dashboard/ dashboards/ identity/ groups/ views.py dashboard/ dashboards/ identity/ projects/ views.py dashboard/ dashboards/ identity/ users/views. py
(cherry picked from commit 8b839938bca245f
Conflicts:
openstack_
openstack_
openstack_