Comment 1 for bug 1123865

Note that this change cannnot be backported to stable/folsom.
----
We alerady decided not to backport it. I would like to share the detail.

Actually auth_token configuration in quantum.conf does not work in stable/folsom
and we cannot backport it. In Folsom, keystone provides auth_token middleware and this middle does not check the configurations in quantum.conf.

In Grizzly, auth_token middleware is moved to keystoneclient and this middleware is enhanced
to check the auth_token configurations in the configurations in the main application in addition to api-paste.ini. "auth_token" middleware also exists in keystone and it is a wrapper to call keystoneclient auth_token. This provides backward compatibility with Folsom.
----