What you need
- an idea of which messengers and email your audience uses;
- a machine for the Veriqa server;
- access to the app’s code where the SMS code is sent and checked today.
Steps
1
Match the channels to your audience
The list of channels is on the Supported channels page. The Email
channel covers users who have no messenger but do have email.
2
Deploy the Veriqa server
In Docker, follow the self-hosted quickstart; without Docker,
install it as an OS service.
3
Enable the channels
Set up the channels you chose as described in Channel setup.
5
Keep SMS as a fallback
During the switch, offer sign-in through Veriqa as the main option and the SMS code as a fallback
for users no channel suits. Remove the fallback once almost nobody uses it.
6
Move operation confirmations too
If the SMS code also confirmed operations, not just sign-in, replace it with a repeated sign-in and
an
auth_time check — see Second factor and step-up.How to check
Sign in to the app through a messenger: the sign-in should succeed, and your SMS gateway should receive no requests. Then check that the SMS fallback still works.Next steps
- Replacing SMS codes — what changes for the user and for you;
- How Veriqa differs — the comparison with SMS codes and where it stops applying;
- Confirming a sensitive operation — if SMS confirmed transfers and changes of account details.