From 5c91ede44768ebbb2fff12f9a7c93e63b9bbd56d Mon Sep 17 00:00:00 2001 From: Jamie Lennox Date: Tue, 11 Mar 2014 15:59:10 +1000 Subject: Plugin loading from config objects Provide a pattern for auth plugins to load themselves from a config object. The first user of this will be auth_token middleware however it is not likely to be the only user. By doing this in an exportable way we are defining a single config file format for specifying how to load a plugin for all services. We also provide a standard way of retrieving a plugins options for loading via other mechanisms. Blueprint: standard-client-params Change-Id: I353b26a1ffc04a20666e76f5bd2f1e6d7c19a22d --- setup.cfg | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'setup.cfg') diff --git a/setup.cfg b/setup.cfg index ee649b8..3e55932 100644 --- a/setup.cfg +++ b/setup.cfg @@ -31,6 +31,12 @@ setup-hooks = console_scripts = keystone = keystoneclient.shell:main +keystoneclient.auth.plugin = + v2password = keystoneclient.auth.identity.v2:Password + v2token = keystoneclient.auth.identity.v2:Token + v3password = keystoneclient.auth.identity.v3:Password + v3token = keystoneclient.auth.identity.v3:Token + [build_sphinx] source-dir = doc/source build-dir = doc/build -- cgit v1.2.1