Domain token confused with domain context in identity panels

[Radomir Dopieralski]

With Keystone v2 you only had a domain token when you selected a domain context. This is no longer true for Keystone v3. We need to separate the two concepts in the code, and use the domain context if it is set, and otherwise fall back to effective domain.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/427729
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=8b839938bca245fcb36988ce6dcd3f5d0d96cf3b
Submitter: Jenkins
Branch: master

commit 8b839938bca245fcb36988ce6dcd3f5d0d96cf3b
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: Ifa66d8c397e34d16a4534e7216eb11c752699505

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/434193

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/434542

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/434193
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=df369b4c1255ee89303fd82f4da3388e8e480c07
Submitter: Jenkins
Branch: stable/newton

commit df369b4c1255ee89303fd82f4da3388e8e480c07
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: Ifa66d8c397e34d16a4534e7216eb11c752699505
    (cherry picked from commit 8b839938bca245fcb36988ce6dcd3f5d0d96cf3b)
    Conflicts:
     openstack_dashboard/dashboards/identity/groups/views.py
     openstack_dashboard/dashboards/identity/projects/views.py
     openstack_dashboard/dashboards/identity/users/views.py

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/434542
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=1227d3eb1407c03e0005cdf8c705d86189491cbd
Submitter: Jenkins
Branch: stable/ocata

commit 1227d3eb1407c03e0005cdf8c705d86189491cbd
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: Ifa66d8c397e34d16a4534e7216eb11c752699505
    (cherry picked from commit 8b839938bca245fcb36988ce6dcd3f5d0d96cf3b)