Closed zlwaterfield closed 2 days ago
Hey @zlwaterfield! 👋 This pull request seems to contain no description. Please add useful context, rationale, and/or any other information that will help make sense of this change now and in the distant Mars-based future.
2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
chromium
: 0 added, 2 modified, 0 deleted (diff for shard 1)webkit
: 0 added, 0 modified, 0 deletedTriggered by this commit.
Amazing
3 snapshot changes in total. 0 added, 3 modified, 0 deleted:
chromium
: 0 added, 3 modified, 0 deleted (diff for shard 1, diff for shard 2)webkit
: 0 added, 0 modified, 0 deletedTriggered by this commit.
Size Change: -448 B (-0.04%)
Total Size: 1.16 MB
1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
chromium
: 0 added, 1 modified, 0 deleted (diff for shard 2)webkit
: 0 added, 0 modified, 0 deletedTriggered by this commit.
Problem
Our 2FA experience is not good, we use a pre generated server side UI that's buggy and doesn't let users view, generated or rolled backup codes or disable 2FA
Changes
This PR updates all the 2FA functionality to be on the PostHog user settings page (view backup codes, generate backup codes, disable 2FA)
Before:
After:
Does this work well for both Cloud and self-hosted?
It doesn't have an impact.
How did you test this code?
Manually and behind ff.