login. If this is your first login, you will need to follow the device approval workflow. This is only needed once, as an extra layer of security to trust the device you are on.
3would need to be entered, followed by the TOTP code. Enter the corresponding number to proceed:
2fa_duration=30_daysto prompt for 2FA every 30 days, or...
2fa_duration=foreverto never prompt again on this device
config.jsonfile is created, if one does not exist. By default, the config file is created at ~/.keeper on MacOS and Linux, and at C:\Users\.keeper on Windows.
serverKeeper data center region
debugenable or disable detailed crypto and network logging
pluginsSet which password rotation plugin will be loaded.
commandsComma-separated list of Keeper commands to run
timedelayRun the specified commands every X seconds.
"timedelay":600will run the commands every 10 minutes.
private_keyDevice private key generated by Commander on a new device. This key is used to encrypt and decrypt vault data.
device_tokenDevice token generated by the backend for every new device. The device token is used to uniquely identify the device, and it controls the session behavior.
commandsfield allows for predetermined commands to be run on login.
config.jsonfile for each instance as long as all of the fields are populated, and the device identifier has been "approved".
config.jsonfile in order to resume a session automatically.
config.jsonfile. Example file:
test.cmdwith the following lines:
@in front of the command to suppress the possible command error.