)]}'
{"quantum/agent/metadata/agent.py":[{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"12f092ce383af5a98603f9437beb229d4c2e5a6f","unresolved":false,"context_lines":[{"line_number":79,"context_line":"        )"},{"line_number":80,"context_line":"        #FIXME bug 1150051 There are no public api to get auth_token"},{"line_number":81,"context_line":"        # from client, so we are copying auth_token from property"},{"line_number":82,"context_line":"        self.auth_token \u003d qclient.httpclient.auth_token"},{"line_number":83,"context_line":"        return qclient"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"    @webob.dec.wsgify(RequestClass\u003dwsgi.Request)"}],"source_content_type":"text/x-python","patch_set":3,"id":"AAAAN3%2F%2F5qc%3D","line":82,"updated":"2013-03-07 03:15:37.000000000","message":"I have not understood why it works. keystone authentication is called the first time HTTP access is called, so in a case of the first call of _get_quantum_client qclient.httpclient.auth_token is None at this timing. And there is no chance to set a valid token to self.auth_token later. Thus I am afraid self.auth_token is always None. I hope my understanding is correct.\n\nIn addition, if non-None token is passed in the constructor Client(), we also needs to pass end_pointurl, but we don\u0027t know the end_pointurl at this point. This behavior of quantumclient is implemented before keystone auth is introduced and we can improve it at the client side.","commit_id":"23c841a86a8815c3de07a5c261cda4c50e174303"}]}