b39132daa0
The entire purpose of this confusingly named middleware is to take token values out of headers and put them into a dictionary. There's no point in this, we have a request class that can abstract this for us. Deprecate the middleware, it's unnecessary. bp: deprecated-as-of-rocky Change-Id: I09310bab6bd728127288ba4c3cf8f884a31e2b98
17 lines
884 B
YAML
17 lines
884 B
YAML
---
|
|
prelude: >
|
|
The token_auth middleware functionality has been merged into the main auth
|
|
middleware (keystone.middleware.auth.AuthContextMiddleware).
|
|
`admin_token_auth` must be removed from the [pipeline:api_v3],
|
|
[pipeline:admin_api], and [pipeline:public_api] sections of your paste ini
|
|
file. The [filter:token_auth] block will also need to be removed from your
|
|
paste ini file. Failure to remove these elements from your paste ini file
|
|
will result in keystone to no longer start/run when the `token_auth` is
|
|
removed in the Stein release.
|
|
upgrade:
|
|
- Remove token_auth from your keystone paste.ini file. Failure to remove
|
|
these elements from your paste ini file will result in keystone to no
|
|
longer start/run when the `token_auth` is removed in the Stein release.
|
|
deprecations:
|
|
- The keystone.middleware.core:TokenAuthMiddleware is deprecated for removal.
|