All keystone middleware components should reuse the auth context prepared
by AuthContextMiddleware. Note that AuthContextMiddleware is listed in
etc/keystone-paste.ini as one of the earliest middleware components in the
keystone pipeline. This means that almost all other middleware components
can depend on the auth context being available for use.
Also added a test to check that a trust cannot be retrived in case of a
missing auth context. Such a request should throw Forbidden exception.
Reviewed: https:/ /review. openstack. org/190863 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=288a05a4de4 b61d32816081f4c 2a0f6e2f773cf2
Committed: https:/
Submitter: Jenkins
Branch: master
commit 288a05a4de4b61d 32816081f4c2a0f 6e2f773cf2
Author: Deepti Ramakrishna <email address hidden>
Date: Thu Jun 11 13:32:52 2015 -0700
Reuse token_ref fetched in AuthContextMidd leware.
All keystone middleware components should reuse the auth context prepared leware. Note that AuthContextMidd leware is listed in keystone- paste.ini as one of the earliest middleware components in the
by AuthContextMidd
etc/
keystone pipeline. This means that almost all other middleware components
can depend on the auth context being available for use.
Also added a test to check that a trust cannot be retrived in case of a
missing auth context. Such a request should throw Forbidden exception.
Change-Id: I1c08976cf4d175 fa2cfe2e39fe558 11f04f13243
Closes-Bug: #1433211