Closed subhojit777 closed 5 years ago
After reading https://auth0.com/docs/flows/concepts/regular-web-app-login-flow, decided that the current implementation of GET /answers-get
is fine. It calls https://api.github.com/user
with the access token to validate the request. In every API call which would require data from GitHub, the application should use the access token and validate it with https://api.github.com/user
or something.
Current GET
/answers-get
is using the access token to authenticate API calls. It is callingGET https://api.github.com/user
with the token and returning output based on the response.Repetitive calls to
GET https://api.github.com/user
is not possible, therefore find a way to cache the authentication, and invalidate it.See #1