Lost keys when upgrading to 4.x whilst using proxy header authentication

[RichyHBM]

Describe the bug
Upgrading to 4.0 caused me to lose all my authenticators due to email changing when using
AUTHENTICATION_GUARD=reverse-proxy-guard
AUTH_PROXY_HEADER_FOR_USER=HTTP_REMOTE_USER

From what I can tell in the account page, my email changed from fake.email@do.not.use in 3.x to admin@remote on 4.x

To Reproduce
Steps to reproduce the behavior:

1. Using Proxy auth header, on 3.4.x add some keys
2. Upgrade to 4.x
3. Open and notice no keys shown

Expected behavior
Migration should keep details

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS] Windows
• Browser [e.g. chrome, safari] Chrome/Brave
• Version [e.g. 22] 4.0.1

Additional context
Add any other context about the problem here.

[RichyHBM]

For anyone seeing similar issue, to fix it manually I had to open the sqlite file in an editor and set the user_id column on the keys to the user id of your account

[Bubka]

Hi,
You speak about security keys I guess?
If so, having no security key after upgrade is the expected situation.

From the change log/release notes:

2FAuth uses a new component to operate the WebAuthn authentication that cannot use existing registrations of your security devices. As a consequence, all your security devices will be revoked and the "Use Webauthn only" option will be disabled during the upgrade to avoid any issue and/or lockout. You will have to sign in using your email and password to re-register you security devices.

[pwlgrzs]

For anyone seeing similar issue, to fix it manually I had to open the sqlite file in an editor and set the user_id column on the keys to the user id of your account

That worked, thank you!

[Bubka]

@RichyHBM @pwlgrzs Before upgrading, did you ever created an account in your 2Fauth instance (using the registration form) or did you started using it directly with the remote user setup?

[pwlgrzs]

I think the setup running now was straight remote user, but I cannot recall anymore :<

[Bubka]

I was able to reproduce, I think this is this condition that leads to the situation.
The fix suggested by Richy is ok but should be extended to the groups table if you use them. I'm working on a fix right now.