-
Notifications
You must be signed in to change notification settings - Fork 29
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
Demo not accessible via given credentials #7
Comments
Works for me. |
Not working here (401, no much info in the console) |
Thank you for raising this. You're probably all correct, there are two straightforward reasons why it may not work:
Maybe there's other reasons but these are the ones that pop to mind. Fortunately, these are non issues for private instances but these issues can be improved on nonetheless. For one, we should carry over the private key between wipes. #2 is a bit harder to tackle, since one can run arbitrary SQL queries. That said, we should better protect against accidents like deleting the last admin or deleting oneself. TrailBase does parse the SQL queries into an AST, so we could best-effort protect against schema changes of system tables. |
Looking into this a bit more, I had already fixed the key persistence issue in the past. It's likely just #2 or even simpler: folks logging in and changing the password. I started to wipe the instance more often now. Not a solution but should at least make the impact less severe. |
...and this is why we can't have nice things. |
No description provided.
The text was updated successfully, but these errors were encountered: