Fix issue #160. Refresh SignedJwtAssertionCredentials w/Storage.

Fixes refreshing a SignedJwtAssertionCredentials w/Storage. There were two issues, first private_key was binary and not serializable into JSON, and secondly the access_token wasn't being restored when reading from JSON.

Also fix up some logging to use named loggers.

Fixes issue #160.

[aiuto, 2012-07-11 18:46:53]

lgtm

http://codereview.appspot.com/6346086/diff/1/oauth2client/client.py
File oauth2client/client.py (right):

http://codereview.appspot.com/6346086/diff/1/oauth2client/client.py#newcode828
oauth2client/client.py:828: 
do you need this blank line?

http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py
File tests/test_oauth2client_jwt.py (right):

http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py#n...
tests/test_oauth2client_jwt.py:232: private_key = datafile('privatekey.p12')
Just a question. Does this test flow actually verify the private_key is p12, or
could you used any valid base64 encoded string here?

http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py#n...
tests/test_oauth2client_jwt.py:257: 
either no blank here, or put it in at line 239

[jcgregorio_google, 2012-07-11 19:31:45]

http://codereview.appspot.com/6346086/diff/1/oauth2client/client.py
File oauth2client/client.py (right):

http://codereview.appspot.com/6346086/diff/1/oauth2client/client.py#newcode828
oauth2client/client.py:828: 
No. Removed.

On 2012/07/11 18:46:53, aiuto wrote:
> do you need this blank line?

http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py
File tests/test_oauth2client_jwt.py (right):

http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py#n...
tests/test_oauth2client_jwt.py:232: private_key = datafile('privatekey.p12')
It actually must be a valid p12 file as the underlying signing code gets called.

On 2012/07/11 18:46:53, aiuto wrote:
> Just a question. Does this test flow actually verify the private_key is p12,
or
> could you used any valid base64 encoded string here?

http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py#n...
tests/test_oauth2client_jwt.py:257: 
On 2012/07/11 18:46:53, aiuto wrote:
> either no blank here, or put it in at line 239

Done.

[aiuto, 2012-07-11 19:34:11]

lgtm again

[jcgregorio_google, 2012-07-11 19:36:28]

Committed in
http://code.google.com/p/google-api-python-client/source/detail?r=59a3057af22...

On 2012/07/11 19:31:45, jcgregorio_google wrote:
> http://codereview.appspot.com/6346086/diff/1/oauth2client/client.py
> File oauth2client/client.py (right):
> 
> http://codereview.appspot.com/6346086/diff/1/oauth2client/client.py#newcode828
> oauth2client/client.py:828: 
> No. Removed.
> 
> On 2012/07/11 18:46:53, aiuto wrote:
> > do you need this blank line?
> 
> http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py
> File tests/test_oauth2client_jwt.py (right):
> 
>
http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py#n...
> tests/test_oauth2client_jwt.py:232: private_key = datafile('privatekey.p12')
> It actually must be a valid p12 file as the underlying signing code gets
called.
> 
> On 2012/07/11 18:46:53, aiuto wrote:
> > Just a question. Does this test flow actually verify the private_key is p12,
> or
> > could you used any valid base64 encoded string here?
> 
>
http://codereview.appspot.com/6346086/diff/1/tests/test_oauth2client_jwt.py#n...
> tests/test_oauth2client_jwt.py:257: 
> On 2012/07/11 18:46:53, aiuto wrote:
> > either no blank here, or put it in at line 239
> 
> Done.