[
https://issues.apache.org/jira/browse/LIBCLOUD-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400637#comment-15400637
]
ASF subversion and git services commented on LIBCLOUD-835:
----------------------------------------------------------
Commit 78df34cf8db8706440ee594c571d80de8613433e in libcloud's branch
refs/heads/trunk from [~paul.tiplady]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=78df34c ]
Fix caching of Google auth tokens
_write_token_to_file was not zeroing the file before writing
a new token, causing corruption.
FIXES: LIBCLOUD-835
Closes #844
Signed-off-by: Tomaz Muraus <[email protected]>
> Malformed auth token causes fatal exception in Google Storage driver
> --------------------------------------------------------------------
>
> Key: LIBCLOUD-835
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-835
> Project: Libcloud
> Issue Type: Bug
> Reporter: Paul Tiplady
> Priority: Critical
>
> One of my Django instances has started hitting a libcloud error which is
> causing a fatal exception, bringing down the instance.
> It looks like libcloud is writing invalid JSON into the auth token, which
> then causes a JSON parse error when it is subsequently read back in.
> Here's the token that's written:
> {code}
> $ cat /root/.google_libcloud_auth.<project>
> {"access_token": "<redacted>", "token_type": "Bearer", "expire_time":
> "2016-07-12T16:45:09Z", "expires_in": 3559}09Z", "expires_in": 3537}
> {code}
> Note the two "expires_in" keys, one with a nonsense value of `3559}09Z"`
> Environment:
> Python 3.4.4
> apache-libcloud==1.0.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
