Radomir Dopieralski df369b4c12 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: Ifa66d8c397e34d16a4534e7216eb11c752699505 (cherry picked from commit 8b839938bc) Conflicts: openstack_dashboard/dashboards/identity/groups/views.py openstack_dashboard/dashboards/identity/projects/views.py openstack_dashboard/dashboards/identity/users/views.py		2017-02-15 11:08:22 +01:00
..
templates/groups	Correct the description for "Update Group" form	2016-07-08 00:46:52 +00:00
__init__.py	Separating Identity Dashboard and using RBAC	2014-08-18 16:40:56 -06:00
constants.py	Separating Identity Dashboard and using RBAC	2014-08-18 16:40:56 -06:00
forms.py	Disentangle domain context from effective domain	2017-02-15 11:08:22 +01:00
panel.py	Retrieve domain scoped token	2016-03-08 15:17:38 -08:00
tables.py	Server-side filtering for Identity	2016-09-13 10:06:27 -05:00
tests.py	Disentangle domain context from effective domain	2017-02-15 11:08:22 +01:00
urls.py	Update URLs to Django 1.8+ style	2016-03-28 11:03:08 +01:00
views.py	Disentangle domain context from effective domain	2017-02-15 11:08:22 +01:00