| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The V3 token plugin should work for v3 identity service
Change-Id: Ic3c53dd94e1fe5d1ab69a02a7f7469735ee4c978
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A common case is for Nova (or other service) to create a service
authentication plugin from a configuration file and then have many
greenlet threads that want to reuse that authentication. If a token
expires then many threads all try and fetch a new token to use and can
step over each other.
I was hoping for a way to put a lock in so that all plugins were thread
safe however fixing it for identity plugins solves almost all real world
situations and anyone doing non-identity plugins will have to manage
threads themselves.
Change-Id: Ib6487de7de638abc69660c851bd048a8ec177109
Closes-Bug: #1493835
|
| |
|
|
|
|
|
| |
Add some documentation regarding the existence of generic plugins. Those
that can be used against the v2 or v3 APIs.
Change-Id: Ie52f0653e20cbc9338481f874aaefa4cdee97116
|
| |
|
|
|
|
|
|
|
|
|
| |
These are the plugins that will be available for use by auth_token
middleware and other services as they adopt sessions.
There needs to be a good way to document the config parameters that each
plugin exposes, because these are not necessarily the same as what are
available via __init__.
Change-Id: I4ad8ea89381be7571c8a30a6fcd9162c259eb581
|
| |
|
|
|
|
|
|
| |
Similar to the other authentication methods that were documented,
like password and token, this patch will add a brief description
on how to authenticate with the oauth1 plugin.
Change-Id: I1b7cceb116d337be71576139601f34ca17563a50
|
|
|
Explain the plugins that are provided and some information on how to
write new ones. This will obviously need to be expanded as more features
are added.
Change-Id: Ie67e93f2ed994c3702ac66e388cf216609dd44ff
|
