Does the new GITHUB OAUTH marker produce all previous ones?

I have an application fully written in Javascript that makes extensive use of the Github API. The fact is that if you open it in two browsers (for example, Chrome and Firefox) and log in as the same user, the second OAUTH token will now become the last token - the token in the first browser stops working immediately.

Is this the expected behavior? Is it possible to allow tokens to live even after new ones are released for the user? Or do I need to provide some kind of token store on my server for each user and continue to pull / push the last token to all current clients?

In other words, what's the best way to support OAuth tokens for multiple clients of a single application?

+5
source share
1 answer

Is this the expected behavior? Is it possible to let tokens live on even ones after new ones are released for the user? Or do I need to provide some kind of token store on my server for each user and keep pulling / pressing the last token on all current clients?

Yes, I would suggest putting this functionality in the api and keep the token side of the tokens and provide a json api. How do I do with tastyrepo.com

+1
source

All Articles