Document the auth plugins that are loadable by name
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
This commit is contained in:
@@ -119,6 +119,22 @@ access token's key and secret. For example::
|
|||||||
>>> s = session.Session(auth=a)
|
>>> s = session.Session(auth=a)
|
||||||
|
|
||||||
|
|
||||||
|
Loading Plugins by Name
|
||||||
|
=======================
|
||||||
|
|
||||||
|
In auth_token middleware and for some service to service communication it is
|
||||||
|
possible to specify a plugin to load via name. The authentication options that
|
||||||
|
are available are then specific to the plugin that you specified. Currently the
|
||||||
|
authentication plugins that are available in `keystoneclient` are:
|
||||||
|
|
||||||
|
- password: :py:class:`keystoneclient.auth.identity.generic.Password`
|
||||||
|
- token: :py:class:`keystoneclient.auth.identity.generic.Token`
|
||||||
|
- v2password: :py:class:`keystoneclient.auth.identity.v2.Password`
|
||||||
|
- v2token: :py:class:`keystoneclient.auth.identity.v2.Token`
|
||||||
|
- v3password: :py:class:`keystoneclient.auth.identity.v3.Password`
|
||||||
|
- v3token: :py:class:`keystoneclient.auth.identity.v3.Token`
|
||||||
|
|
||||||
|
|
||||||
Creating Authentication Plugins
|
Creating Authentication Plugins
|
||||||
===============================
|
===============================
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user