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
Is your feature request related to a problem? Please describe.
If a user creates a temporary queue, and he signs in after that, the created queue is still not owned by anyone.
Describe the solution you'd like
All created ownerless queues when the user signs in should change to being owner by the user. This can be done by creating a random token and sending it when a temporary queue/token is created and send this token as the queue owner in the backend and store this token in local storage. When the user signs in, make a backend call to transfer ownership from this token to the user who logged in.
The text was updated successfully, but these errors were encountered:
daltonfury42
changed the title
Signed in users should be the owners of their existing queues created in the same session
Signed in users should be the owners of their existing queues created in the same device
Feb 4, 2021
As a first step, I've added a unique device UUID which will be sent with every unauthenticated request to the backend. So, from now own, every anonymous user will see only their own queues.
Now we need to add a backend endpoint to migrate all resources created against such a UUID to a user and call it after the user logs in.
Is your feature request related to a problem? Please describe.
If a user creates a temporary queue, and he signs in after that, the created queue is still not owned by anyone.
Describe the solution you'd like
All created ownerless queues when the user signs in should change to being owner by the user. This can be done by creating a random token and sending it when a temporary queue/token is created and send this token as the queue owner in the backend and store this token in local storage. When the user signs in, make a backend call to transfer ownership from this token to the user who logged in.
The text was updated successfully, but these errors were encountered: