From 8010e773accce2d24c04659c88ac0c040c9a1932 Mon Sep 17 00:00:00 2001 From: Bhuvan Arumugam Date: Wed, 22 Aug 2012 15:57:59 -0700 Subject: [PATCH] Document the use of keyring. * README.rst Document the option --os-use-keyring, and environment variable OS_USE_KEYRING, to enable keyring. Change-Id: I54ceb2d2692fecca328da16f6ed14db8d09a6eb7 --- README.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.rst b/README.rst index 4ea7000d4..b8e26c9fa 100644 --- a/README.rst +++ b/README.rst @@ -67,6 +67,7 @@ The 'password flow' variation is most commonly used:: export OS_TENANT_NAME= export OS_USERNAME= export OS_PASSWORD= # (optional) + export OS_USE_KEYRING=true # (optional) The corresponding command-line options look very similar:: @@ -74,9 +75,12 @@ The corresponding command-line options look very similar:: --os-tenant-name --os-username [--os-password ] + [--os-use-keyring] If a password is not provided above (in plaintext), you will be interactively -prompted to provide one securely. +prompted to provide one securely. If keyring is enabled, the password entered +in the prompt is stored in keyring. From next time, the password is read from +keyring, if it is not provided above (in plaintext). The token flow variation for authentication uses an already-aquired token and a URL pointing directly to the service API that presumably was acquired