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

add option for mid test troubleshooting #41

Open
3 tasks
thrombe opened this issue Sep 12, 2024 · 0 comments
Open
3 tasks

add option for mid test troubleshooting #41

thrombe opened this issue Sep 12, 2024 · 0 comments

Comments

@thrombe
Copy link
Collaborator

thrombe commented Sep 12, 2024

user might need to change their network, or they might need to reboot due to technical problems.

but simply allowing this willy-nilly is bad.
some sort of system where they need to ask the test providers for a key would be better.

make the server have an admin api route that returns small one time tokens to temporarily disable the proctoring and return the explorer back to working state.

the idea here is that any user can ask the admins for one of these tokens when they want to troubleshoot. troubleshooting would be done in the presence of a proctor ideally.

remember to / suggestions:

  • token expiration within a few minutes of creation.
  • disable the actual test when troubleshooting
  • would be better if the app does not need network access for the troubleshooting option
    • one way would be to have some sort system similar to OTP. (a simple time based salted algorithm. server generates the token, and it is checked with the same algo inside app. this seems fine here - as the user is not supposed to have any electronic devices which might be able to run this algorithm)
    • another way could be to leverage public key cryptography. have the server generate a small token, and have the client verify it
@thrombe thrombe changed the title add option to quit the app mid test for troubleshooting add option for mid test troubleshooting Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant