Document of authorize about passport HOT 4 CLOSED

This looks good to me. In fact, it's almost the exact schema I use in my own applications.

Tokens are never stored in the session. I always store them in the Account schema, and use them when making calls to any 3rd-party API. One thing I typically do is save the token each time the user signs on, if the token is different. This helps catch tokens that expired in case a user returns to your site after a long time period. In other cases, I have background tasks that refresh tokens for which offline access is granted (like Google or Facebook).

Let me know if you have any other questions.

from passport.

Ah, tokens are used when make a third-party API request. Thanks. Let me ask one more question?
I will get different tokens when user login with different browsers or devices. But do I need to store tokens as Array? Isn't it enough to update the lastest token because I need just one token when I make a request?

from passport.

In general, yes, you should always store the latest token that the third-party has issued to your app. A single field should be sufficient for that case.

from passport.

Thanks for reply newbie question. It's grate help for my current personal development.

from passport.