Ensure to always use unscoped token to rescope

Bug #1474893 reported by Lin Hua Cheng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
django-openstack-auth
Fix Released
Medium
Lin Hua Cheng

Bug Description

unscoped token should be always use when rescoping token.

For keystone v3, when the user initially fetch the token, it would default to scoped token if there is a default project setup.

We need to enforce that we always fetch an unscoped token, by making an explicit call to fetch unscoped token

Changed in django-openstack-auth:
assignee: nobody → Lin Hua Cheng (lin-hua-cheng)
David Lyle (david-lyle)
Changed in django-openstack-auth:
importance: Undecided → Medium
milestone: none → 1.3.2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to django_openstack_auth (master)

Fix proposed to branch: master
Review: https://review.openstack.org/202224

Changed in django-openstack-auth:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to django_openstack_auth (stable/kilo)

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/203095

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on django_openstack_auth (stable/kilo)

Change abandoned by Lin Hua Cheng (<email address hidden>) on branch: stable/kilo
Review: https://review.openstack.org/203095

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to django_openstack_auth (master)

Reviewed: https://review.openstack.org/202224
Committed: https://git.openstack.org/cgit/openstack/django_openstack_auth/commit/?id=e4062e37069d58814b7c09299d3018297a75ba1d
Submitter: Jenkins
Branch: master

commit e4062e37069d58814b7c09299d3018297a75ba1d
Author: lin-hua-cheng <email address hidden>
Date: Wed Jul 15 11:13:38 2015 -0700

    Use unscoped token for scoping to project

    When authenticating a user in v3, always request
    for an unscoped token. Otherwise it would automatically
    default to the default project.

    Change-Id: I9e1d9129e2fb35933c803096fca9f1236affc27f
    Closes-Bug: #1474893

Changed in django-openstack-auth:
status: In Progress → Fix Committed
Changed in django-openstack-auth:
milestone: none → 1.4.0
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to django_openstack_auth (stable/kilo)

Reviewed: https://review.openstack.org/203095
Committed: https://git.openstack.org/cgit/openstack/django_openstack_auth/commit/?id=11a7d124ab148b6d4c418b87ae61548de22cd422
Submitter: Jenkins
Branch: stable/kilo

commit 11a7d124ab148b6d4c418b87ae61548de22cd422
Author: lin-hua-cheng <email address hidden>
Date: Wed Jul 15 11:13:38 2015 -0700

    Use unscoped token for scoping to project

    When authenticating a user in v3, always request
    for an unscoped token. Otherwise it would automatically
    default to the default project.

    Change-Id: I9e1d9129e2fb35933c803096fca9f1236affc27f
    Closes-Bug: #1474893
    (cherry picked from commit e4062e37069d58814b7c09299d3018297a75ba1d)

tags: added: in-stable-kilo
Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/django_openstack_auth 1.2.1

This issue was fixed in the openstack/django_openstack_auth 1.2.1 release.

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.