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.

Sign up for GitHub

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

Jump to bottom

Use token in WS communication #68

Closed
recap opened this issue Jun 12, 2024 · 0 comments · Fixed by #69
Closed

Use token in WS communication #68

recap opened this issue Jun 12, 2024 · 0 comments · Fixed by #69

Comments

@recap
Copy link
Member

recap commented Jun 12, 2024 •
edited
Loading

Currently using WS a user could potentially bypass the token and queue himself to any experiment. The token should be added to all WS communication so validation can be done at every step
@recap recap linked a pull request Jun 12, 2024 that will close this issue
68 use token in ws communication #69
Merged
@recap recap closed this as completed in #69 Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

68 use token in ws communication obeliss-nlesc/otree-waiting-room
1 participant
@recap