You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2018. It is now read-only.
Right now "logging in" basically means that a successful response is returned when a request is made with an Authorization header. In the web app we login in by retrieving and storing the user JSON record in the sessionStorage and sending the user/pwd in each successive request. We need a better system that:
Removes all locks held by the user. (when we implement editing locks)
Returns a session token so we don't have to store the user/pwd in the browser, that has an expiration date,
Supports a /logout that revokes the session token.
Creates an auth history table that stores session tokens and keeps a history of user logins and logouts.
If we could drop in an OAuth or OAuth2 implementation that would be best.
The text was updated successfully, but these errors were encountered:
Right now "logging in" basically means that a successful response is returned when a request is made with an Authorization header. In the web app we login in by retrieving and storing the user JSON record in the sessionStorage and sending the user/pwd in each successive request. We need a better system that:
If we could drop in an OAuth or OAuth2 implementation that would be best.
The text was updated successfully, but these errors were encountered: