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
The idea is to detect IP address changes, combined with device fingerprint to detect session theft.
(Edited version based on feedbacks)
IP change detection: Revoke access token, this will force reuse the refresh token which can then be used to detect token theft. This will also prevent logouts due to false positives.
Device fingerprint change=> Revoke access token
Questions to solve:
What is considered as a reliable device fingerprint?
On web
On mobile
How do we compute/encode it?
This would be done from the Front end, so possible for an attacker to reverse engineer, but adds an additional layer of complexity to a session theft attack.
The above would only work if the access token has blacklisting turned on. How should we deal with the case when blacklisting is off?
The text was updated successfully, but these errors were encountered:
If the IP has changed, even within the same city, we will only revoke the access token. This will force reuse the refresh token which can then be used to detect token theft. This will also prevent logouts due to false positives.
If the device fingerprint has changed, then we will revoke the entire session.
Discussion
The above would only work if the access token has blacklisting turned on. How should we deal with the case when blacklisting is off?
Summary
The idea is to detect IP address changes, combined with device fingerprint to detect session theft.
(Edited version based on feedbacks)
IP change detection: Revoke access token, this will force reuse the refresh token which can then be used to detect token theft. This will also prevent logouts due to false positives.
Device fingerprint change=> Revoke access token
Questions to solve:
The text was updated successfully, but these errors were encountered: