Update OTP page and screenshots
29
OTP.md
@@ -8,9 +8,6 @@ KeePassDX is compatible with the algorithms:
|
||||
# 2FA Token Generator
|
||||
Thanks to the TOTP generation function, **it is possible to use theKeePassDX app as a token generator for external services using two-factor authentication (2FA)**.
|
||||
|
||||
[[images/OTP/entry_TOTP.jpg]]
|
||||
This example indicates a generated TOTP token (present in the TOTP field) that can be used to log into your Google account.
|
||||
|
||||
_**Please note**: Authentication with several factors does not necessarily mean TOTP.
|
||||
Indeed, 2FA is a concept which is also used for unlocking a KeePass database. If a database is encrypted with a password **and** a keyfile, the database uses two authentication factors.
|
||||
Not to be confused with the generation of tokens by KeePassDX, used to open external accounts (Google, Amazon, etc.)_
|
||||
@@ -27,13 +24,27 @@ For example, if you have a two-factor Google authentication, it is recommended t
|
||||
KeePassDX can use the links generated by QR codes to register new OTP keys. But KeePassDX does not contain a QR code reader, other apps are dedicated to that and do the job very well.
|
||||
|
||||
So you just have to use your favorite code reader app (ie: [QR & Barcode Scanner](https://github.com/dmitriy-ilchenko/QrAndBarcodeScanner)) and share the link to KeePassDX:
|
||||
1. Open your database in modification
|
||||
2. Scan your QR code with a compatible app
|
||||
3. Share the link to KeePassDX (ie: "share as text")
|
||||
4. KeePassDX switches to "Save" mode
|
||||
5. Select an entry (the otp field of the entry is automatically filled)
|
||||
|
||||
1. Scan your QR code with a compatible app
|
||||
|
||||
2. Share the link to KeePassDX (ie: "share as text")
|
||||
|
||||
[[images/OTP/share_otp.jpg]]
|
||||
|
||||
3. KeePassDX switches to "Save" mode, open your database if necessary
|
||||
|
||||
[[images/OTP/save_mode.jpg]]
|
||||
|
||||
5. Select or create an entry (the otp field of the entry is automatically filled)
|
||||
|
||||
[[images/OTP/save_mode_otpauth.jpg]]
|
||||
|
||||
6. Save the entry
|
||||
|
||||
7. Voilà! The OTP token is automatically generated
|
||||
|
||||
[[images/OTP/entry_TOTP.jpg]]
|
||||
|
||||
8. Check that your QR code reader app does not have a history, if so, delete the data.
|
||||
|
||||
## Manually
|
||||
@@ -57,4 +68,4 @@ Steam unfortunately does not use the standardized TOTP algorithms, but instead a
|
||||
# Autofill
|
||||
The autofill of OTP tokens is very complicated and cannot be generalized because most forms do not use a standardized format and different metadata, so it is not possible to identify the fields to be filled in.
|
||||
To overcome this problem, the most efficient solution is to copy the OTP token directly from the list of entries in KeePassDX (make sure the `Settings - Appearance - Show OTP Token` is activated)
|
||||
Associated issue: https://github.com/Kunzisoft/KeePassDX/issues/553#issuecomment-912936390
|
||||
Associated issue: https://github.com/Kunzisoft/KeePassDX/issues/553#issuecomment-912936390
|
||||
|
||||
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 42 KiB |
|
Before Width: | Height: | Size: 20 KiB After Width: | Height: | Size: 42 KiB |
BIN
images/OTP/save_mode.jpg
Normal file
|
After Width: | Height: | Size: 46 KiB |
BIN
images/OTP/save_mode_otpauth.jpg
Normal file
|
After Width: | Height: | Size: 45 KiB |
BIN
images/OTP/share_otp.jpg
Normal file
|
After Width: | Height: | Size: 42 KiB |