Comment 10 for bug 1252248

Reviewed: https://review.openstack.org/57438
Committed: http://github.com/openstack/python-heatclient/commit/2706b48159e8937b4ef266f194a158ba60e2f36d
Submitter: Jenkins
Branch: master

commit 2706b48159e8937b4ef266f194a158ba60e2f36d
Author: Steven Hardy <email address hidden>
Date: Wed Nov 20 13:22:44 2013 +0000

    Make tokens work with --os-no-client-auth

    Currently --os-no-client-auth assumes you'll only ever want to pass
    a username and password to the standalone auth_password middleware,
    but it's also valid to pass a token and endpoint, which can then
    be used to either connect to a normal (non-standalone) Heat without
    needing the client to connect to keystone, or pass a token to custom
    auth middleware in standalone mode where tokens are accepted.

    e.g:

    heat --os-no-client-auth
          --heat-url http://127.0.0.1:8004/v1/<tenant ID>
          --os-auth-token <a token> stack-list

    Change-Id: Ie22c85ba5b3b987505f4d6204b4dd6ff03e0d912
    Closes-Bug: #1252248