📍How we managed to improve the situation around the problem of app sharing.
📍What methods did we use to combat the problem?
📍What results were obtained and how they were measured.
📍And also how you can do it even better and why all this is needed.
6. Multi-factor Authentication (MFA)?
ka8725
Possible Solution Simple
Needs more data
from user Precise
OK for long
run
Business is OK
with it
Third-party Y N N N Y
Logs analysis N N N Y Y
Limit by device
type Y N Y Y N
MFA via phone Y Y Y Y N
MFA via
Authenticator Y Y Y Y N
MFA via email Y N Y Y Y
Consider solutions
11. Multi-factor Authentication (MFA)?
Indicators
- Number of signups per day/week/month
- Users’ Retention (how many leave/stay)
- Number of login sessions per user
- Revenue (in Stripe)
ka8725
12. Multi-factor Authentication (MFA)?
Our expectations
- Number of signups per day/week/month
- Users Retention (how many leave/stay)
- Number of login sessions per user
- Revenue (in Stripe)
ka8725
13. Multi-factor Authentication (MFA)?
Collect Data
- Paper_trail gem for history of signups/subscription changes
- Login_sessions table. It’s ID is injected into cookies
User logs in -> login session record created
logs out -> login session gets deactivated
ka8725
25. Multi-factor Authentication (MFA)?
How we implemented MFA
- Devise-two-factor gem. The codes sent via email
- “Remember” the code pass in cookies 30 days
ka8725