<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 07/28/2016 10:05 PM, Tim Hinrichs
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAJjxPADX8ZKTc2wxsBwZbvdnUS+5iA_0GoanCp5xgcqNqKfGTg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        I've never worked on the authentication details, so this may be
        off track, but that error message indicates the failure is
        happening inside Congress's oslo_policy.  
        <div><br>
        </div>
        <div>Error message shows up here as a Python exception class.</div>
        <div><a moz-do-not-send="true"
href="https://github.com/openstack/congress/blob/master/congress/exception.py#L135">https://github.com/openstack/congress/blob/master/congress/exception.py#L135</a><br>
        </div>
        <div><br>
        </div>
        <div>That exception class is instantiated only here</div>
        <a moz-do-not-send="true"
href="https://github.com/openstack/congress/blob/master/congress/common/policy.py#L93">https://github.com/openstack/congress/blob/master/congress/common/policy.py#L93</a>
        <div><br>
        </div>
        <div>The code that uses the instantiated exception class (which
          actually does the enforcement):</div>
        <div><a moz-do-not-send="true"
href="https://github.com/openstack/congress/blob/7c2f4132b9693e7969e704cb9914963274c2c4a1/congress/api/webservice.py#L373">https://github.com/openstack/congress/blob/7c2f4132b9693e7969e704cb9914963274c2c4a1/congress/api/webservice.py#L373</a><br>
        </div>
        <div><br>
        </div>
        <div>
          <div>I don't remember off the top of my head how the default
            policy.json gets created, but I'm sure the admin credentials
            will work.  You might want to ensure you're logged in as the
            admin with...</div>
          <div><br>
          </div>
          <div>$ source openrc admin admin</div>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    IN most projects, policy is enforced against an oslo-context
    object.  That shouild abstract away the differences between V2 and
    V3 keystone token formats.<br>
    <br>
    Make sure that the policy is not dying on something specific to one
    version or the other.  Post the actual rule executed, please.<br>
    <br>
    <br>
    <blockquote
cite="mid:CAJjxPADX8ZKTc2wxsBwZbvdnUS+5iA_0GoanCp5xgcqNqKfGTg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br class="inbox-inbox-Apple-interchange-newline">
        </div>
        <div>Tim</div>
        <div><br>
        </div>
        <div>
          <div class="gmail_quote">
            <div dir="ltr">On Thu, Jul 28, 2016 at 1:56 PM Aimee Ukasick
              <<a moz-do-not-send="true"
                href="mailto:aimeeu.opensource@gmail.com"
                target="_blank">aimeeu.opensource@gmail.com</a>>
              wrote:<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">I've
              gotten a little farther, which leads me to my next
              question -<br>
              does the API support v3 token auth?<br>
              or am I making mistakes in my manual testing?<br>
              <br>
              using the CLI on local devstack<br>
              1) did not modify openrc<br>
              2) source openrc<br>
              3) openstack token issue<br>
              4)  openstack congress datasource list --os-auth-type
              v3token<br>
              --os-token ad74073300e244768e08e0d4cd73fbbd --os-auth-url<br>
              <a moz-do-not-send="true"
                href="http://192.168.56.101:5000/v3" rel="noreferrer"
                target="_blank">http://192.168.56.101:5000/v3</a><br>
              --os-project-id da9a9ba573c34c18a037fd04812d81bc   --debug
              --verbose<br>
              <br>
              When the python-congressclient calls the API, this is the
              response:<br>
              RESP BODY: Policy doesn't allow get_v1 to be performed.<br>
              Request returned failure status: 403<br>
              <br>
              Log:  <a moz-do-not-send="true"
                href="http://paste.openstack.org/show/543445/"
                rel="noreferrer" target="_blank">http://paste.openstack.org/show/543445/</a><br>
              <br>
              So then I called the API directly:<br>
              curl -X POST -H "Content-Type: application/json" -H
              "Cache-Control: no-cache"<br>
              -d '{ "auth": {<br>
                  "identity": {<br>
                    "methods": ["password"],<br>
                    "password": {<br>
                      "user": {<br>
                        "name": "demo",<br>
                        "domain": { "id": "default" },<br>
                        "password": "secret"<br>
                      }<br>
                    }<br>
                  }<br>
                }<br>
              }' "<a moz-do-not-send="true"
                href="http://192.168.56.101:5000/v3/auth/tokens"
                rel="noreferrer" target="_blank">http://192.168.56.101:5000/v3/auth/tokens</a>"<br>
              <br>
              Response:<br>
              {<br>
                "token": {<br>
                  "issued_at": "2016-07-28T20:43:44.258137Z",<br>
                  "audit_ids": [<br>
                    "N6tnfbI5QvyRT4xEB7pGCA"<br>
                  ],<br>
                  "methods": [<br>
                    "password"<br>
                  ],<br>
                  "expires_at": "2016-07-28T21:43:44.258112Z",<br>
                  "user": {<br>
                    "domain": {<br>
                      "id": "default",<br>
                      "name": "Default"<br>
                    },<br>
                    "id": "f2bf5189bbd7466cbecc1b1315cff3b5",<br>
                    "name": "demo"<br>
                  }<br>
                }<br>
              }<br>
              <br>
              Then:<br>
              curl -X GET -H "X-Auth-Token:
              f2bf5189bbd7466cbecc1b1315cff3b5" -H<br>
              "Cache-Control: no-cache" "<a moz-do-not-send="true"
                href="http://192.168.56.101:1789/v1/data-sources"
                rel="noreferrer" target="_blank">http://192.168.56.101:1789/v1/data-sources</a>"<br>
              <br>
              Response:<br>
              {<br>
                "error": {<br>
                  "message": "The request you have made requires
              authentication.",<br>
                  "code": 401,<br>
                  "title": "Unauthorized"<br>
                }<br>
              }<br>
              <br>
              I'm feeling pretty stupid at the moment, like I've missed
              something obvious.<br>
              Any ideas?<br>
              <br>
              Thanks!<br>
              <br>
              aimee<br>
              <br>
              On Fri, Jul 22, 2016 at 9:21 PM, Anusha Ramineni <<a
                moz-do-not-send="true"
                href="mailto:anusha.iiitm@gmail.com" target="_blank">anusha.iiitm@gmail.com</a>>
              wrote:<br>
              > Hi Aimee,<br>
              ><br>
              > Thanks for the investigation.<br>
              ><br>
              > I remember testing congress client with V3 password
              based authentication ,<br>
              > which worked fine .. but never tested with token
              based .<br>
              ><br>
              > Please go ahead and fix it , if you think there is
              any issue .<br>
              ><br>
              ><br>
              > On 22-Jul-2016 9:38 PM, "Aimee Ukasick" <<a
                moz-do-not-send="true"
                href="mailto:aimeeu.opensource@gmail.com"
                target="_blank">aimeeu.opensource@gmail.com</a>>
              wrote:<br>
              >><br>
              >> All - I made the change to the auth_url that 
              Anusha suggested.<br>
              >> Same problem as before " Cannot authorize API
              client"<br>
              >> 2016-07-22 14:13:50.835861 ***** calling
              policies_list =<br>
              >> client.list_policy()*****<br>
              >> 2016-07-22 14:13:50.836062 Unable to get policies
              list: Cannot<br>
              >> authorize API client.<br>
              >><br>
              >> I used the token from the log output to query the
              Congress API with<br>
              >> the keystone v3 token - no issues.<br>
              >> curl -X GET -H "X-Auth-Token:
              18ec54ac811b49aa8265c3d535ba0095" -H<br>
              >> "Cache-Control: no-cache" "<a
                moz-do-not-send="true"
                href="http://192.168.56.103:1789/v1/policies"
                rel="noreferrer" target="_blank">http://192.168.56.103:1789/v1/policies</a>"<br>
              >><br>
              >> So I really think the problem is that the
              python-congressclient<br>
              >> doesn't support identity v3.<br>
              >> I thought it did, but then I came across this:<br>
              >> "support keystone v3 api and session based
              authentication "<br>
              >> <a moz-do-not-send="true"
                href="https://bugs.launchpad.net/python-congressclient/+bug/1564361"
                rel="noreferrer" target="_blank">https://bugs.launchpad.net/python-congressclient/+bug/1564361</a><br>
              >> This is currently assigned to Anusha.<br>
              >> I'd like to start work on it since I am becoming
              familiar with keystone<br>
              >> v3.<br>
              >><br>
              >> Thoughts?<br>
              >><br>
              >> aimee<br>
              >><br>
              >><br>
              >><br>
              >><br>
              >> On Fri, Jul 22, 2016 at 8:07 AM, Aimee Ukasick<br>
              >> <<a moz-do-not-send="true"
                href="mailto:aimeeu.opensource@gmail.com"
                target="_blank">aimeeu.opensource@gmail.com</a>>
              wrote:<br>
              >> > Thanks Anusha! I will retest this today. I
              guess I need to learn more<br>
              >> > about Horizon as well - thanks for pointing
              me in the right direction.<br>
              >> ><br>
              >> > aimee<br>
              >> ><br>
              >> ><br>
              >> ><br>
              >> > On Fri, Jul 22, 2016 at 6:30 AM, Anusha
              Ramineni<br>
              >> > <<a moz-do-not-send="true"
                href="mailto:anusha.iiitm@gmail.com" target="_blank">anusha.iiitm@gmail.com</a>>
              wrote:<br>
              >> >> Hi Aimee,<br>
              >> >><br>
              >> >> I think devstack by default configured
              horizon to use v3 .<br>
              >> >> For V2 authentication, from the logs ,
              auth_url doesn't seem to be set<br>
              >> >> explicitly to v2 auth_url .<br>
              >> >><br>
              >> >> I have always set explicit v2 auth which
              worked fine.<br>
              >> >> For eg:- auth_url =
              '<a class="moz-txt-link-freetext" href="http://">http://</a><host-ip>:5000/v2.0' , for V2<br>
              >> >> authentication<br>
              >> >><br>
              >> >> I have raised a patch, to take the
              auth_url from horizon settings<br>
              >> >> instead of<br>
              >> >> from request.<br>
              >> >> <a moz-do-not-send="true"
                href="https://review.openstack.org/#/c/345828/1"
                rel="noreferrer" target="_blank">https://review.openstack.org/#/c/345828/1</a><br>
              >> >><br>
              >> >> Please set explict v2 auth_url as
              mentioned above in<br>
              >> >> OPENSTACK_KESYTONE_URL<br>
              >> >> in
              <horizon>/openstack_dashboard/local/local_settings.py
              and restart<br>
              >> >> apache2<br>
              >> >> server . Then v2 authentication should
              go through fine.<br>
              >> >><br>
              >> >> For v3 , need to add relevant code for
              v3 authentication in<br>
              >> >> contrib/horizon<br>
              >> >> as presently it is hardcoded to use only
              v2. but yes, the code from<br>
              >> >> plugin<br>
              >> >> model patch is still a WIP , so doesn't
              work for v3 authentication I<br>
              >> >> guess<br>
              >> >> I'll have a look at it and let you know
              .<br>
              >> >><br>
              >> >><br>
              >> >> Best Regards,<br>
              >> >> Anusha<br>
              >> >><br>
              >> >> On 21 July 2016 at 21:56, Tim Hinrichs
              <<a moz-do-not-send="true" href="mailto:tim@styra.com"
                target="_blank">tim@styra.com</a>> wrote:<br>
              >> >>><br>
              >> >>> So clearly an authentication problem
              then.<br>
              >> >>><br>
              >> >>> Anusha, do you have any ideas? 
              (Aimee, I think Anusha has worked with<br>
              >> >>> Keystone authentication most
              recently, so she's your best bet.)<br>
              >> >>><br>
              >> >>> Tim<br>
              >> >>><br>
              >> >>> On Thu, Jul 21, 2016 at 8:59 AM
              Aimee Ukasick<br>
              >> >>> <<a moz-do-not-send="true"
                href="mailto:aimeeu.opensource@gmail.com"
                target="_blank">aimeeu.opensource@gmail.com</a>>
              wrote:<br>
              >> >>>><br>
              >> >>>> The  Policy/Data Sources web
              page throws the same errors. I am<br>
              >> >>>> planning to recheck direct API
              calls using v3 auth today or tomorrow.<br>
              >> >>>><br>
              >> >>>> aimee<br>
              >> >>>><br>
              >> >>>> On Thu, Jul 21, 2016 at 10:49
              AM, Tim Hinrichs <<a moz-do-not-send="true"
                href="mailto:tim@styra.com" target="_blank">tim@styra.com</a>>
              wrote:<br>
              >> >>>> > Hi Aimee,<br>
              >> >>>> ><br>
              >> >>>> > Do the other APIs work? 
              That is, is it a general problem<br>
              >> >>>> > authenticating, or<br>
              >> >>>> > is the problem limited to
              list_policies?<br>
              >> >>>> ><br>
              >> >>>> > Tim<br>
              >> >>>> ><br>
              >> >>>> > On Wed, Jul 20, 2016 at
              3:54 PM Aimee Ukasick<br>
              >> >>>> > <<a
                moz-do-not-send="true"
                href="mailto:aimeeu.opensource@gmail.com"
                target="_blank">aimeeu.opensource@gmail.com</a>><br>
              >> >>>> > wrote:<br>
              >> >>>> >><br>
              >> >>>> >> Hi all,<br>
              >> >>>> >><br>
              >> >>>> >> I've been working on
              Policy UI (Horizon): Unable to get policies<br>
              >> >>>> >> list (devstack) (<a
                moz-do-not-send="true"
                href="https://bugs.launchpad.net/congress/+bug/1602837"
                rel="noreferrer" target="_blank">https://bugs.launchpad.net/congress/+bug/1602837</a>)<br>
              >> >>>> >> for the past 3 days.
              Anusha is correct - it's an authentication<br>
              >> >>>> >> problem, but I have not
              been able to fix it.<br>
              >> >>>> >><br>
              >> >>>> >> I grabbed the relevant
              code in congress.py from Anusha's horizon<br>
              >> >>>> >> plugin model patchset (<a
                moz-do-not-send="true"
                href="https://review.openstack.org/#/c/305063/3"
                rel="noreferrer" target="_blank">https://review.openstack.org/#/c/305063/3</a>)<br>
              >> >>>> >> and<br>
              >> >>>> >> added try/catch blocks,
              logging statements (with error because I<br>
              >> >>>> >> haven't figured out how
              to set the horizon log level).<br>
              >> >>>> >><br>
              >> >>>> >><br>
              >> >>>> >> I am testing the code
              on devstack, which I cloned on 19 July 2016.<br>
              >> >>>> >><br>
              >> >>>> >> With both v2 and v3
              auth, congressclient.v1.client is created.<br>
              >> >>>> >> The failure happens
              trying to call<br>
              >> >>>> >>
              congressclient.v1.client.Client.list_policies().<br>
              >> >>>> >> When using v2 auth, the
              error message is "Unable to get policies<br>
              >> >>>> >> list:<br>
              >> >>>> >> The resource could not
              be found"<br>
              >> >>>> >> When using v3 auth, the
              error message is "Cannot authorize API<br>
              >> >>>> >> client"<br>
              >> >>>> >><br>
              >> >>>> >> I am assuming that
              congressclient.v1.client.Client is<br>
              >> >>>> >><br>
              >> >>>> >><br>
              >> >>>> >><br>
              >> >>>> >> <a
                moz-do-not-send="true"
href="https://github.com/openstack/python-congressclient/blob/master/congressclient/v1/client.py"
                rel="noreferrer" target="_blank">https://github.com/openstack/python-congressclient/blob/master/congressclient/v1/client.py</a><br>
              >> >>>> >> and that
              client.list_policy() calls list_policy()in the<br>
              >> >>>> >> python-congressclient<br>
              >> >>>> >> which in turn calls the
              Congress API. Is this correct?<br>
              >> >>>> >><br>
              >> >>>> >> Any ideas why with v3
              auth, the python-congressclient cannot<br>
              >> >>>> >> authorize<br>
              >> >>>> >> the<br>
              >> >>>> >> call to the API?<br>
              >> >>>> >><br>
              >> >>>> >> I looked at other
              horizon plugin models (ceilometer, neutron,<br>
              >> >>>> >> nova,<br>
              >> >>>> >> cerberus, cloudkitty,
              trove, designate, manila) to see how they<br>
              >> >>>> >> created<br>
              >> >>>> >> the client. While the
              code to create a client is not identical,<br>
              >> >>>> >> it is vastly different
              from the code to create a client<br>
              >> >>>> >> in
              contrib/horizon/congress.py.<br>
              >> >>>> >><br>
              >> >>>> >> Thanks in advance for
              any pointers.<br>
              >> >>>> >><br>
              >> >>>> >> aimee<br>
              >> >>>> >><br>
              >> >>>> >> Aimee Ukasick (aimeeu)<br>
              >> >>>> >><br>
              >> >>>> >> v2 log:<br>
              >> >>>> >> 2016-07-20
              22:13:56.501455<br>
              >> >>>> >> 2016-07-20
              22:14:30.238233 ***** view.get_data calling policies =<br>
              >> >>>> >>
              congress.policies_list(self.request) *****<br>
              >> >>>> >> 2016-07-20
              22:14:30.238318 ***** self.request.path=<br>
              >> >>>> >>
              /dashboard/admin/policies/<br>
              >> >>>> >> 2016-07-20
              22:14:30.238352 ***** congress.policies_list(request)<br>
              >> >>>> >> BEGIN*****<br>
              >> >>>> >> 2016-07-20
              22:14:30.238376 ***** calling client =<br>
              >> >>>> >>
              congressclient(request)*****<br>
              >> >>>> >> 2016-07-20
              22:14:30.238399 ***** congress.congressclient<br>
              >> >>>> >> BEGIN*****<br>
              >> >>>> >> 2016-07-20
              22:14:30.238454 ***** auth_url=<br>
              >> >>>> >> <a
                moz-do-not-send="true"
                href="http://192.168.56.103/identity" rel="noreferrer"
                target="_blank">http://192.168.56.103/identity</a><br>
              >> >>>> >> 2016-07-20
              22:14:30.238479 ***** calling get_keystone_session<br>
              >> >>>> >> *****<br>
              >> >>>> >> 2016-07-20
              22:14:30.238505 ***** congress.get_keystone_session<br>
              >> >>>> >> BEGIN<br>
              >> >>>> >> auth_url *****<a
                moz-do-not-send="true"
                href="http://192.168.56.103/identity" rel="noreferrer"
                target="_blank">http://192.168.56.103/identity</a><br>
              >> >>>> >> 2016-07-20
              22:14:30.238554 ***** path= /identity<br>
              >> >>>> >> 2016-07-20
              22:14:30.238578 ***** using V2 plugin to<br>
              >> >>>> >> authenticate*****<br>
              >> >>>> >> 2016-07-20
              22:14:30.238630 ***** v2 auth.get_auth_state=<br>
              >> >>>> >> 2016-07-20
              22:14:30.238656 None<br>
              >> >>>> >> 2016-07-20
              22:14:30.238677 ***** finished using V2 plugin to<br>
              >> >>>> >> authenticate*****<br>
              >> >>>> >> 2016-07-20
              22:14:30.238698 ***** creating session with auth *****<br>
              >> >>>> >> 2016-07-20
              22:14:30.244407 ***** congress.get_keystone_session<br>
              >> >>>> >> END*****<br>
              >> >>>> >> 2016-07-20
              22:14:30.244462 ***** regtion_name= RegionOne<br>
              >> >>>> >> 2016-07-20
              22:14:30.244491 ***** calling<br>
              >> >>>> >>
              congress_client.Client(**kwargs)<br>
              >> >>>> >> 2016-07-20
              22:14:30.247830 ***** congress.congressclient END*****<br>
              >> >>>> >> 2016-07-20
              22:14:30.247902 ***** calling policies_list =<br>
              >> >>>> >>
              client.list_policy()*****<br>
              >> >>>> >> 2016-07-20
              22:14:30.248012 DEBUG:keystoneauth.identity.v2:Making<br>
              >> >>>> >> authentication request
              to <a moz-do-not-send="true"
                href="http://192.168.56.103/identity/tokens"
                rel="noreferrer" target="_blank">http://192.168.56.103/identity/tokens</a><br>
              >> >>>> >> 2016-07-20
              22:14:30.255023 DEBUG:keystoneauth.session:Request<br>
              >> >>>> >> returned<br>
              >> >>>> >> failure status: 404<br>
              >> >>>> >> 2016-07-20
              22:14:30.257546 Unable to get policies list: The<br>
              >> >>>> >> resource<br>
              >> >>>> >> could not be found.<br>
              >> >>>> >><br>
              >> >>>> >><br>
              >> >>>> >> v3 log:<br>
              >> >>>> >> 2016-07-20
              22:09:22.912969<br>
              >> >>>> >> 2016-07-20
              22:09:31.907119 ***** view.get_data calling policies =<br>
              >> >>>> >>
              congress.policies_list(self.request) *****<br>
              >> >>>> >> 2016-07-20
              22:09:31.907973 ***** self.request.path=<br>
              >> >>>> >>
              /dashboard/admin/policies/<br>
              >> >>>> >> 2016-07-20
              22:09:31.908122 ***** congress.policies_list(request)<br>
              >> >>>> >> BEGIN*****<br>
              >> >>>> >> 2016-07-20
              22:09:31.908250 ***** calling client =<br>
              >> >>>> >>
              congressclient(request)*****<br>
              >> >>>> >> 2016-07-20
              22:09:31.908386 ***** congress.congressclient<br>
              >> >>>> >> BEGIN*****<br>
              >> >>>> >> 2016-07-20
              22:09:31.909034 ***** auth_url=<br>
              >> >>>> >> <a
                moz-do-not-send="true"
                href="http://192.168.56.103/identity" rel="noreferrer"
                target="_blank">http://192.168.56.103/identity</a><br>
              >> >>>> >> 2016-07-20
              22:09:31.909217 ***** calling get_keystone_session<br>
              >> >>>> >> *****<br>
              >> >>>> >> 2016-07-20
              22:09:31.909356 ***** congress.get_keystone_session<br>
              >> >>>> >> BEGIN<br>
              >> >>>> >> auth_url *****<a
                moz-do-not-send="true"
                href="http://192.168.56.103/identity" rel="noreferrer"
                target="_blank">http://192.168.56.103/identity</a><br>
              >> >>>> >> 2016-07-20
              22:09:31.909527 ***** path= /identity<br>
              >> >>>> >> 2016-07-20
              22:09:31.909795 ***** using V3 plugin to<br>
              >> >>>> >> authenticate*****<br>
              >> >>>> >> 2016-07-20
              22:09:31.910042 auth_url=<a moz-do-not-send="true"
                href="http://192.168.56.103/identity" rel="noreferrer"
                target="_blank">http://192.168.56.103/identity</a><br>
              >> >>>> >> 2016-07-20
              22:09:31.910175 token=d46339f2d0b5455db54909d6ed95a9cc<br>
              >> >>>> >> 2016-07-20
              22:09:31.910301 project_name=alt_demo<br>
              >> >>>> >> 2016-07-20
              22:09:31.910426 domain_name=Default<br>
              >> >>>> >> 2016-07-20
              22:09:31.910676 project_domain_name=default<br>
              >> >>>> >> 2016-07-20
              22:09:31.910866 ***** v3 auth.get_auth_state=<br>
              >> >>>> >> 2016-07-20
              22:09:31.910992 None<br>
              >> >>>> >> 2016-07-20
              22:09:31.914053 ***** finished using V3 plugin to<br>
              >> >>>> >> authenticate*****<br>
              >> >>>> >> 2016-07-20
              22:09:31.914100 ***** creating session with auth *****<br>
              >> >>>> >> 2016-07-20
              22:09:31.922260 ***** congress.get_keystone_session<br>
              >> >>>> >> END*****<br>
              >> >>>> >> 2016-07-20
              22:09:31.922542 ***** regtion_name= RegionOne<br>
              >> >>>> >> 2016-07-20
              22:09:31.922676 ***** calling<br>
              >> >>>> >>
              congress_client.Client(**kwargs)<br>
              >> >>>> >> 2016-07-20
              22:09:31.922822 ***** congress.congressclient END*****<br>
              >> >>>> >> 2016-07-20
              22:09:31.922949 ***** calling policies_list =<br>
              >> >>>> >>
              client.list_policy()*****<br>
              >> >>>> >> 2016-07-20
              22:09:31.924732 Unable to get policies list: Cannot<br>
              >> >>>> >> authorize API client.<br>
              >> >>>> >><br>
              >> >>>> >><br>
              >> >>>> >><br>
              >> >>>> >>
__________________________________________________________________________<br>
              >> >>>> >> OpenStack Development
              Mailing List (not for usage questions)<br>
              >> >>>> >> Unsubscribe:<br>
              >> >>>> >> <a
                moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
              >> >>>> >> <a
                moz-do-not-send="true"
                href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
              >> >>>> ><br>
              >> >>>> ><br>
              >> >>>> ><br>
              >> >>>> ><br>
              >> >>>> >
__________________________________________________________________________<br>
              >> >>>> > OpenStack Development
              Mailing List (not for usage questions)<br>
              >> >>>> > Unsubscribe:<br>
              >> >>>> > <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
              >> >>>> > <a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
              >> >>>> ><br>
              >> >>>><br>
              >> >>>><br>
              >> >>>><br>
              >> >>>>
__________________________________________________________________________<br>
              >> >>>> OpenStack Development Mailing
              List (not for usage questions)<br>
              >> >>>> Unsubscribe:<br>
              >> >>>> <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
              >> >>>> <a moz-do-not-send="true"
                href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
              >> >>><br>
              >> >>><br>
              >> >>><br>
              >> >>>
__________________________________________________________________________<br>
              >> >>> OpenStack Development Mailing List
              (not for usage questions)<br>
              >> >>> Unsubscribe:<br>
              >> >>> <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
              >> >>> <a moz-do-not-send="true"
                href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
              >> >>><br>
              >> >><br>
              >> >><br>
              >> >><br>
              >> >>
__________________________________________________________________________<br>
              >> >> OpenStack Development Mailing List (not
              for usage questions)<br>
              >> >> Unsubscribe:<br>
              >> >> <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
              >> >> <a moz-do-not-send="true"
                href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
              >> >><br>
              >><br>
              >>
__________________________________________________________________________<br>
              >> OpenStack Development Mailing List (not for usage
              questions)<br>
              >> Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
              >> <a moz-do-not-send="true"
                href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
              ><br>
              ><br>
              >
__________________________________________________________________________<br>
              > OpenStack Development Mailing List (not for usage
              questions)<br>
              > Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
              > <a moz-do-not-send="true"
                href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
              ><br>
              <br>
__________________________________________________________________________<br>
              OpenStack Development Mailing List (not for usage
              questions)<br>
              Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
              <a moz-do-not-send="true"
                href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
            </blockquote>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>