Closed GoogleCodeExporter closed 8 years ago
[deleted comment]
[deleted comment]
[deleted comment]
I guess there is should be used some kind of storage, but I didn't find the
setting of this storage in SignedJwtAssertionCredentials and
AssertionCredentials. I found set_store() function in main OAuth2Credentials
class, but seems like it is unused in SignedJwtAssertionCredentials, so the
access token is not kept in it.
Original comment by legato...@gmail.com
on 30 Jun 2012 at 9:23
Alright, I figured out what was the problem.
First of all I've got "invalid_grant" error because system time on my mac was
few seconds ahead. I've tuned the time and now everything works everytime.
Second, I found out that there is a code in SignedJwtAssertionCredentials
resposible to store private_key in storage (to_json and from_json), but this
code is not working.
My source code:
f = file('privatekey.p12', 'rb')
key = f.read()
f.close()
credentials = SignedJwtAssertionCredentials(
'...@developer.gserviceaccount.com',
key,
scope='https://www.googleapis.com/auth/fusiontables')
storage = Storage('fusion.dat')
credentials.set_store(storage)
http = httplib2.Http()
http = credentials.authorize(http)
service = build("fusiontables", "v1", http=http)
print(service.query().sqlGet(sql='SELECT Location FROM
1gvB3SedL89vG5r1128nUN5ICyyw7Wio5g1w1mbk').execute(http))
There is a problem storing private_key as JSON field. Running this code I get
error like this:
UnicodeDecodeError: 'utf8' codec can't decode byte 0x82 in position 1: invalid
start byte
I've tried several approaches to encode private_key, that it can be stored in
Storage, but with no luck. I'll continue to try, but I need an advice.
Original comment by legato...@gmail.com
on 1 Jul 2012 at 12:01
hooray!
So I found the main problem of SignedJwtAssertionCredentials is that it just
does not keep access_token, it refreshing access token on every request, what
takes some time. I solved that problem:
1. I store private_key in Storage object via encoding it in Base64.
2. I've managed to work SignedJwtAssertionCredentials with Storage object to
keep access_token: I've added some fields in constructor of
SignedJwtAssertionCredentials and its parent class – AssertionCredentials.
I've attached new "client.py" from "oauth2client" package. It has all the
discribed changes and it works well.
Original comment by legato...@gmail.com
on 1 Jul 2012 at 12:45
Attachments:
Thanks for finding this, it does look like the issue is storing the private_key
in JSON. I will probably solve it in a slightly different way, by keeping the
base64 encoded value in self.private_key and decoding it when it is needed to
be used, that avoids putting special code in OAuth2Credentials.to_json() that's
only needed for a sub-sub-class.
Original comment by jcgregorio@google.com
on 10 Jul 2012 at 3:26
CL out for review: http://codereview.appspot.com/6346086/
Original comment by jcgregorio@google.com
on 11 Jul 2012 at 2:31
Original comment by jcgregorio@google.com
on 11 Jul 2012 at 4:10
This issue was closed by revision 59a3057af225.
Original comment by jcgregorio@google.com
on 11 Jul 2012 at 7:36
Great! Glad to be useful)
Original comment by legato...@gmail.com
on 12 Jul 2012 at 5:23
Original issue reported on code.google.com by
legato...@gmail.com
on 30 Jun 2012 at 8:38