Accept a verification request from another device.
the input for the accept verification request method
Approve a verification request. Users must check the contents of the [InteractiveVerificationState.ReceivedVerificationData] to ensure the emojis match before approving.
the input for the approve verification method
Cancel the current verification at any time.
the input for the cancel verification method
Create a server-side, encrypted backup of client keys for the user. After creation, keys are automatically uploaded to the backup so this only has to be called once.
the input for the create backup method
a backup key, to be used with the [recover] method to recover keys from the server backup.
Decline a verification request.
the input for the decline verification method
Get the current state of the encrypted server backup.
the input for the get backup state method
the current backup state
Convenience method to check if the current session is verified.
the input for the isVerified method
true if the current session is verified, false otherwise
Get notified when the state of the session verification changes.
the input for the onSessionVerificationChanged method
Register a callback to be notified when a verification request is received.
the input for the on verification request received method
Recover client keys from a server-side backup.
the input for the recover method
Begin an interactive verification flow by requesting verification to another verified, online device.
the input for the request verification method
Resets the backup. This replaces the server side backup with current keys known to this device. This will result in data loss of previous messages encrypted with keys from the previous backup not known to this device. All other devices associated with this user will become unverified.
the input for the reset backup method
a new backup key, to be used with the [recover] method to recover keys from the server backup.
Rotate backup keys. The previous backup key is invalidated and replaced with a new one. Only verified sessions can execute this command.
the input for the rotate backup key method
a new backup key, to be used with the [recover] method to recover keys from the server backup.
Start interactive verification. This can only occur after the other device has accepted the verification request. Either device can start the verification.
the input for the start verification method
Key backup, restore and interactive device verification services.
In the secure communications offering, each device stores their own keys. To seamlessly continue conversations across multiple devices, the keys must be replicated across those devices. Verified devices automatically remain in sync with each others keys, so it's important to design apps that encourage users to keep their devices verified.
Client can verify devices with two mechanisms:
Key backup and restore. In this method, client keys are encrypted with a "backup key" and uploaded to the server. The keys can later be "recovered" on other devices using the same backup key. This backup gives the device access to other previous session keys.
Interactive verification. In this method, two devices can verify their keys out of band using emoji matching. In the case tha verification is happening between the same handle of two different devices, the unverified device becomes verified and will then gain access to session keys from their other devices.