[03:33] *** relrod has quit IRC (Ping timeout: 240 seconds) [03:48] *** relrod_ has joined #arpnetworks [03:48] *** relrod_ has quit IRC (Changing host) [03:48] *** relrod_ has joined #arpnetworks [04:20] *** ziyourenxiang has joined #arpnetworks [06:22] *** mkb_ is now known as mkb [10:04] *** Nahual has joined #arpnetworks [12:09] Sounds like standard 2fa flow, except without the initial 1st factor. 1) User loads login.php (or whatever), 2) login.php generates a random code, stores that in a database and generates a QR code, most likely a URL that includes the token. eg: https://mysite.com/login_with_code.php?code=$randomcode, 3) login_with_code.php prompts the user (on their phone now, because they scanned the QR code and it [12:09] opened their browser) for their login and, assuming validated login, associates session ID 12345 with user ABCD. No need for an overarching library. [14:40] *** relrod_ is now known as relrod [16:24] *** ziyourenxiang has quit IRC (Quit: Leaving) [19:07] *** Nahual has quit IRC (Quit: Leaving.)