You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ankisyncctl.py deluser does not delete the existing sessions in session.db, so the logged device can still sync even if its account has been deleted in auth.db#72
Open
HaujetZhao opened this issue
Jul 4, 2020
· 0 comments
When a device has logged in an account, next time it syncs, sync server won't use auth.db to authorize, the server will check the session.db to see if the session of this device has already build, and then the server will directly sync if the session exists.
Now the problem is, after deleting the account using ankisyncctl.py deluser, the device already logged can still sync, because the session data in the session.db still exists.
So I wish this can be fixed: when deleting a user, also delete the related sessions in session.db.
The text was updated successfully, but these errors were encountered:
HaujetZhao
added a commit
to HaujetZhao/anki-sync-server
that referenced
this issue
Jul 4, 2020
The
auth.db
stores all the accounts.The
session.db
stores all the logged sessions.When a device has logged in an account, next time it syncs, sync server won't use
auth.db
to authorize, the server will check thesession.db
to see if the session of this device has already build, and then the server will directly sync if the session exists.Now the problem is, after deleting the account using
ankisyncctl.py deluser
, the device already logged can still sync, because the session data in thesession.db
still exists.So I wish this can be fixed: when deleting a user, also delete the related sessions in
session.db
.The text was updated successfully, but these errors were encountered: