the complete_qr_login endpoint was returning session.token (the SHA256 hash stored in the database) instead of session.raw_token (the plaintext). this caused all subsequent API calls and WebSocket connections to fail with 401/REFUSED since the server would hash the already-hashed token. adds a regression test that verifies the returned token is usable for authenticated API requests. Reviewed-on: graham/towerops-web#42 |
||
|---|---|---|
| .. | ||
| v1 | ||
| account_data_controller_test.exs | ||
| mobile_auth_controller_test.exs | ||
| mobile_controller_test.exs | ||