/o//commerce-media/accounts/-1/images/18464765?download=true

Mobile Verification
Icon
DXP App
18464384
Now a days, Most of the site needs to verify the mobile number and email address of their users for security purpose. Liferay is providing email verification OOB.

This plugin will help to integrate that functionality directly to the Liferay portal.

Key Features
- Admin can enable/disable mobile verification very easily.
- Mobile verification can be set to be mandatory/optional.
- Further development depending upon mobile verification can be done easily. As mobile number and its status is stored in User Custom Attribute.

Steps to Use

1) Deploy Hook
2) As Admin Go to Control Panel -> Portal Settings -> Authentication
3) Select Tab “SMS”
4) Enable SMS Verification
5) Enter details of Twillio Sms Account, i.e. Account SID, Auth Token, Sending Number
6) Enter the SMS you want to send to mobile number for verification. Add $S where you want to place the verification code. Verification code will be generated automatically and it will replace the $S in the SMS Body.
7) One more check box added for make mandatory. If this is selected. User will be forced to verify the mobile number. If mandatory is not selected. User will get option to skip the verification.

User Site changes for Mobile Verification

1) New text required field is added in the create account page for mobile number. Mobile number will be all digits number with country code in prefix. User don’t need to add plus(+) sign for the number.
2) Once User will enter mobile number and press Save button. One SMS will be sent to the mobile number entered in the field. Popup will open for entering the verification code. User will have to enter the verification code into the field to verify the mobile number.
3) If the mandatory is not selected, User will get a button to skip the verification.

Helping hands :
Vipin Bardia (http://www.liferay.com/web/vipin.bardia/profile)
DEVELOPER
Hardk Rajani
DEVELOPER
11.07.14 00:00
Published date
Fehler bei der Verarbeitung der Vorlage.
The string doesn't match the expected date/time/date-time format. The string to parse was: "11.07.14 00:00". The expected format was: "MM/dd/yy HH:mm".
The nested reason given follows:
Unparseable date: "11.07.14 00:00"

----
FTL stack trace ("~" means nesting-related):
	- Failed at: ${CPDefinition_displayDate.getData()?...  [in template "3192443#3192485#null" at line 4, column 9]
----
1<#setting date_format="MMMMM d, yyyy"> 
2 
3<#if (CPDefinition_displayDate.getData())??> 
4	${CPDefinition_displayDate.getData()?datetime("MM/dd/yy HH:mm")?date} 
5</#if> 
Published Date
11.07.14 00:00
SUPPORTED OFFERINGS
Self-Hosted, Self-Managed
Supported Versions
6.2, 6.1
Resource Requirements
Edition
CE, EE
PRICE
Free
help & support
Terms & Conditions
SHARE LINK
Copy & Share Link

HTML Example

A paragraph is a self-contained unit of a discourse in writing dealing with a particular point or idea. Paragraphs are usually an expected part of formal writing, used to organize longer prose.