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
Currently there is a /login API that must be called to update the user data in the users collection. I do not believe this API should be necessary as we can achieve a similar result by checking if the user data is up to date whenever any API is called with their token.
This login process also contains a migration process intended to update users to use the Core BB. At this point, I believe this process can safely be removed to reduce overhead and simplify logic.
Edit: As of 8/24, there were 434 non-core users out of 70966 users in the prod users collection.
Acceptance Criteria
Whenever a user accesses an API with their token, we should check to see if the user exists, then check if any of their stored data has changed. If it has, we apply an update to the users collection and all memberships with the latest data from the token.
In order to reduce unnecessary database calls, we can cache the user data from the database for some time so subsequent requests will not result in db calls unless the token data changes.
The text was updated successfully, but these errors were encountered:
Description
Currently there is a
/login
API that must be called to update the user data in the users collection. I do not believe this API should be necessary as we can achieve a similar result by checking if the user data is up to date whenever any API is called with their token.This login process also contains a migration process intended to update users to use the Core BB. At this point, I believe this process can safely be removed to reduce overhead and simplify logic.
Edit: As of 8/24, there were 434 non-core users out of 70966 users in the prod users collection.
Acceptance Criteria
Whenever a user accesses an API with their token, we should check to see if the user exists, then check if any of their stored data has changed. If it has, we apply an update to the users collection and all memberships with the latest data from the token.
In order to reduce unnecessary database calls, we can cache the user data from the database for some time so subsequent requests will not result in db calls unless the token data changes.
The text was updated successfully, but these errors were encountered: