summaryrefslogtreecommitdiff
path: root/setup.cfg
diff options
context:
space:
mode:
authorMonty Taylor <mordred@inaugust.com>2015-08-15 07:36:09 +0800
committerMonty Taylor <mordred@inaugust.com>2015-08-15 07:36:09 +0800
commit0cb46c9421c6affef009ca3b1ab54b4f3c176cbe (patch)
tree5e3a95ee2fc156a33174eaf227219642e4df0f3f /setup.cfg
parentc503c29f930638b31c99ed4827ec8a3dd0bde8fe (diff)
downloadpython-keystoneclient-0cb46c9421c6affef009ca3b1ab54b4f3c176cbe.tar.gz
Expose token_endpoint.Token as admin_token
When bootstrapping a cloud, using this auth plugin is necessary to be able to provide an admin token. However, there has been some confusion as to its officialness and the names of its parameters. Make it clear why it's exposed, and additionally be clearer about squatting on the name of the plugin so that things can depend on its interface. Change-Id: I8e896b28d5879cd4b1372009926c67cde773308f
Diffstat (limited to 'setup.cfg')
-rw-r--r--setup.cfg1
1 files changed, 1 insertions, 0 deletions
diff --git a/setup.cfg b/setup.cfg
index e7aa998..b154e53 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -30,6 +30,7 @@ console_scripts =
keystoneclient.auth.plugin =
password = keystoneclient.auth.identity.generic:Password
token = keystoneclient.auth.identity.generic:Token
+ admin_token = keystoneclient.auth.token_endpoint:Token
v2password = keystoneclient.auth.identity.v2:Password
v2token = keystoneclient.auth.identity.v2:Token
v3password = keystoneclient.auth.identity.v3:Password