#01 auth #8
Merged
#01 auth #8
+2,084
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Auth server is pretty much set up.
It will run as a separate node process, other node processes will use the token generated by the server by calling the servers
/credentialsendpoint, which will either return the credentials if they exist, or prompt the user to authenticate through the/authendpoint.After a user authenticates through
/auth, the server will set the credentials, as well as set an interval to refresh the token every 55 minutes (tokens expire every 60 minutes, but there is a 5 minute buffer here). The server will also set a timeout of 13 days (refresh tokens expire every 14 days, we are leaving a 1 day buffer), to clear the refresh token interval, and clear the credentials, which will prompt the user to authenticate again once they try to access/credentials.