KeePassOTP fields
This page lists all data that KeePassOTP stores.
Dependant on the storage approach this fields are either stored within the respective entry or in an additional database which is embedded in the main database.
This field contains all required standard information to calculate an OTP and is stored as protected string.
OTP data is stored in the otpauth format which is described here: OTPAUTH key uri
The entire field will always be stored in an encrypted way.
It will not be decrypted to calculate an OTP.
It will only be decrypted to show it to you in the OTP setup form.
Example 1: otpauth://totp?secret=abcdabcd
Example 2: otpauth://totp/?secret=abcdabcd&algorithm=SHA1&digits=6&period=30
Example 2: otpauth://totp/?secret=abcdabcd&algorithm=SHA1&digits=8&period=15
The first two examples will result in exactly the same OTP being calculated wheras the 3rd example will calculate an OTP with 8 digits that will change every 15 seconds.
You can use KeePassOTP to configure all of the available parameters.
In most of the cases the defaults suggested by KeePassOTP will be just fine.
Advanced settings are hidden by default as they are not required in app. 99.9% of all cases.
If you were explicitly advised to change the default settings, simply display them.
This field is optional and only required in rare cases.
It is stored in the plugin data area - entry tab: Properties
In case of HOTP it is not required at all.
If TOTP is used and there is a huge difference between your computer and the site you want to logon, you can compensate this by providing a specific URL here.
You can also provide OWNURLto always use the URL currently maintained in the entry itself.
KeePassOTP will then query the site's date, compare it with your local time and accomodate for any difference to ensure that the calculated OTP is accepted.