views:

32

answers:

0

I'm succesfully using Signpost to authorize calls to protected resources in a Google account via OAuth.

However it seems a bit weird that the user has to go each and every time through Google and grant access. Is there a way of serializing the Consumer and recreating it so that re-authorization is not needed? I've tried keeping the tokens, secret and verifier in the shared preferences and setting them in the Consumer but I receive a OAuthExpectationFailedException.

Any ideas?