Mobile number verification is designed to prevent fake signups through limiting the amount of trial accounts for a single user. If enabled, this option adds one more field to the activation form, where a user have to type a mobile phone number for getting an SMS or mobile call with an account activation code. Herewith, one number could be bound to a single account only.
For this type of verification to be operable, you need to preliminary set up either a supplemental SMS-sending tool (e.g. Twilio), or, as a more secure alternative, a phone call verification service (for example - OnVerify)
By default, the registration form is configured for the SMS verification usage (whilst the way it can be adjusted for confirmation via call is described within the linked above doc on OnVerify appliance).So, a
fter a user clicks the Send/Get a Call
button under the specified phone number, the 4-cell field for entering the received verification code will appear below:
In case an SMS/call wasn’t received, a user can either Edit the phone number (if it was specified incorrectly) or Contact support (if any other issue occurred). Also, the amount of tries for the verification code entering is limited per each phone number and can be configured via JCA.
The users’ experience during a new account creation with SMS/call verification enabled is described in the Account Registration document.
Enabling Mobile Phone Verification
So, in order to add mobile phone verification to the activation form, perform the following steps:
1. Navigate to the JCA > System Settings
section, enable the Expert mode
and expand the common
2. Double-click on the signup.verification.method quota and state the SMS value for it (for both message or call verification; the default one is NONE).
Mobile phone verification will work only in case signup.activation.enabled
is set to true
and the appropriate tool (e.g. Twilio
) is configured to convey an activation code
In such a way, all the new users will be obliged to pass the check with an activation code, received via mobile phone number.
Setting the Amount of Code Input Attempts
In order to control the limit of tries for entering the received activation code, the signup.sms.code.attempts quota (located within the System Settings > common JCA section whilst the Expert mode enabled) is used, which default value is 5.
If a user exceeds the stated amount of incorrect code input attempts, the verification will be failed. In this case, the remaining way to complete the registration is to specify another phone number.