Graham McIntire
33daaf14f0
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 |
||
|---|---|---|
| .. | ||
| channels | ||
| components | ||
| controllers | ||
| graphql | ||
| helpers | ||
| integration | ||
| live | ||
| plugs | ||
| graphql_socket_test.exs | ||
| permissions_test.exs | ||
| plug_exceptions_test.exs | ||
| remote_ip_test.exs | ||
| telemetry_filter_test.exs | ||
| user_auth_test.exs | ||