diff options
| author | Dolph Mathews <dolph.mathews@gmail.com> | 2012-07-13 14:54:24 -0500 |
|---|---|---|
| committer | Dolph Mathews <dolph.mathews@gmail.com> | 2012-07-13 14:54:27 -0500 |
| commit | 540c4883d6f2de25dd38db0c18d59d568cd35f1e (patch) | |
| tree | 731bcf9336b497f96c9335dcbaca24df83b9484b | |
| parent | 6d911d2d41dbe91edf2c8a56eebccfb5a1a3469d (diff) | |
| download | python-openstackclient-540c4883d6f2de25dd38db0c18d59d568cd35f1e.tar.gz | |
Secure password prompt (docs)
Change-Id: I879a8aba13318f1dd660a487cbd1fd20c7ae659b
| -rw-r--r-- | README.rst | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -66,14 +66,17 @@ The 'password flow' variation is most commonly used:: export OS_AUTH_URL=<url-to-openstack-identity> export OS_TENANT_NAME=<tenant-name> export OS_USERNAME=<user-name> - export OS_PASSWORD=<password> # yes, it isn't secure, we'll address it in the future + export OS_PASSWORD=<password> # (optional) The corresponding command-line options look very similar:: --os-auth-url <url> --os-tenant-name <tenant-name> --os-username <user-name> - --os-password <password> + [--os-password <password>] + +If a password is not provided above (in plaintext), you will be interactively +prompted to provide one securely. The token flow variation for authentication uses an already-aquired token and a URL pointing directly to the service API that presumably was acquired |
