Short answer: moving email login off a managed provider transfers responsibility for session revocation to your application, so make single-use email verification, refresh-token rotation, and a durable revocation decision part of the migration contract before moving users. A delivered magic link proves neither that verification succeeded nor that a stolen session stopped working. For an education platform, the acceptance test is concrete: after revoking one learner's compromised session, its refresh tokens must stop producing credentials, and protected requests must obey the documented access-token revocation policy.
What page fired when the stolen session kept working?
Consider this hypothetical production exercise: I am reviewing a migration for a learning platform, a learner reports a stolen session, and the responder revokes it while an attacker holds its refresh token. This is a scenario to test, not a report of an observed incident.…