Caching access tokens for reuse

[hadynz]

This is not a bug; more of a question to see what ideas are used out there.

When a user logs in via google-signin, a user object is returned similar to the following:

accessToken: "ya29.hQJD767t_-geYHlFUyW9CCAGBC"
accessTokenExpirationDate: 3599.984444022179
email: "email@gmail.com"
id: "1003109889901343"
idToken: "eyJhbGciOiJSUzI1NiIsImtpZCI6ImYwMmZkODgwOTNmNTQ2Mjg1MD"
name: "My name"
photo: "https://lh5.googleusercontent.com/-/8elejb5_N1A/s120/photo.jpg"
serverAuthCode: "4/4eGtD4XPGKnIGxUUVhVe96XYBz11Y"

The accessToken is what I use when invoking various google api endpoints which I plan to be doing fairly frequently whilst the user is using my app.

Is it expected that I cache this user object for 3599 seconds before needing to re-sign the user? Or would I call a google endpoint to refresh the token, and aim to keep the token alive all the time?

Thoughts?

[skleest]

+1 -- any ideas?

[tuananhtd]

I think "keep the token alive all the time" is not ideal. If you want some performance optimization (reduce some additional requests) then just keep track of the expiration date of the token and only refresh it when needed. If you are lazy like me then just always refresh it before use :d

[vonovak]

In an effort to clean the issues up, this is being closed. Please open a new issue if you're experiencing a problem.