Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signed in users should be the owners of their existing queues created in the same device #477

Open
maaverik opened this issue Jan 17, 2021 · 1 comment
Assignees
Labels
full-stack Requires work to be done at backend too

Comments

@maaverik
Copy link
Collaborator

maaverik commented Jan 17, 2021

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.

@maaverik maaverik added the full-stack Requires work to be done at backend too label Jan 17, 2021
@daltonfury42 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
@daltonfury42 daltonfury42 self-assigned this Feb 21, 2021
@navaneeth-spotnana
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
full-stack Requires work to be done at backend too
Projects
None yet
Development

No branches or pull requests

3 participants