| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |
| Who | What | When |
|---|---|---|
| *** | relrod has quit IRC (Ping timeout: 240 seconds) | [03:33] |
| .... (idle for 15mn) | ||
| relrod_ has joined #arpnetworks
relrod_ has quit IRC (Changing host) relrod_ has joined #arpnetworks | [03:48] | |
| ....... (idle for 32mn) | ||
| ziyourenxiang has joined #arpnetworks | [04:20] | |
| ......................... (idle for 2h2mn) | ||
| mkb_ is now known as mkb | [06:22] | |
| ............................................. (idle for 3h42mn) | ||
| Nahual has joined #arpnetworks | [10:04] | |
| .......................... (idle for 2h5mn) | ||
| brycec | 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
opened their browser) for their login and, assuming validated login, associates session ID 12345 with user ABCD. No need for an overarching library. | [12:09] |
| ............................... (idle for 2h31mn) | ||
| *** | relrod_ is now known as relrod | [14:40] |
| ..................... (idle for 1h44mn) | ||
| ziyourenxiang has quit IRC (Quit: Leaving) | [16:24] | |
| ................................. (idle for 2h43mn) | ||
| Nahual has quit IRC (Quit: Leaving.) | [19:07] | |
| ↑back Search ←Prev date Next date→ Show only urls | (Click on time to select a line by its url) |