Refresh a token (Multiple Oauth2Clients)

So, i was reading the docs and i saw the only way to refresh a token is this

oauth2client.on('tokens', (tokens) => {
  if (tokens.refresh_token) {
    // store the refresh_token in my database!
    console.log(tokens.refresh_token);
  }
  console.log(tokens.access_token);
});

Isn’t it inefficient to add an event to every single client? isn’t there a better way to manually check the clients access token and refresh it using the refresh token?

[mrdulin]

@richardpeng I agree.

@bcoe The tokens event can’t access application context. Where should I put this .on("tokens") in application code?

For example, if use express, the context info is attached in req object, like req.user

I think below way is wrong:

app.post('/post', (req, res) => {
  auth.on('tokens', async (tokens) => {
    const requestingUser = req.user
    const user = await db.findByEmail(requestingUser.email)
    await db.updateGoogleAccountTokensByUser(user)
  })
})

If put auth.on('tokens', (tokens) => {}) on a global environment

auth.on('tokens', (tokens) => {
  // Don't know whose tokens
  const user = ??
  await db.updateGoogleAccountTokensByUser(user)
})

[fabiofcferreira]

Hey! I randomly came across this issue and I actually wanted to ask something very similar to @supertiger1234 asked.

What if I want to save the new token to the database? Using the listener becomes very hard in that matter. What is your suggestion?