I have a client that forced 2-factor authentication for staff. They have a staging site that restores backups from the production site. My security key won’t work on the staging site, but Google Authenticator codes will. I don’t know if this is a feature, a bug, or something about how security key…

Thanks for that, makes perfect sense. Security keys as per the specification are tied to a single hostname as the “Relaying Party”, so keys defined in production will not work for staging.

Can you define what you mean when you say security keys “won’t work”? Do you get any errors? Can you add security keys in your second factor preferences successfully? Is the problem with using them on login?

Sorry. That wasn’t very helpful. “Try a different security Key. You’re using a security key that’s not registered with this website”. I guess maybe that’s coming from Chrome and it remembered the hostname of the production server?

Zwei-Faktor-Login auf der Staging-Site

Unterstützung

martin (Martin Brennan) 19. Februar 2020 um 23:37 4

Danke dafür, das ergibt absolut Sinn. Sicherheitsschlüssel gemäß der Spezifikation sind an einen einzelnen Hostnamen als „Relying Party

Thema		Antworten	Aufrufe
Cannot use registered U2F if hostname has changed Feature	3	708	21. August 2020
Logging in with security key fails when triggered by keyboard navigation Bug	2	326	31. März 2023
Cannot complete 2FA with TOTP code if verifying with security key fails Bug	1	571	4. November 2021
Second factor landing page, register multiple TOTP keys Feature	3	1198	12. August 2019
Two Factor local login proposal Feature	44	9566	6. März 2018

Zwei-Faktor-Login auf der Staging-Site

Verwandte Themen