In this section we implement the login interface for Larabbs small programs


In the third tutorial, we’ve added the interface for mobile registration and WeChat login, so Larabbs can use:
Cell phone
WeChat Login Sign in in in three ways.

As mentioned in the previous section, if the public platform is bound to other WeChat applications and small programs, then UnionId can be used to get the only WeChat user, but because we do not have a real WeChat mobile phone app or web application, so do not discuss.

The scenario for a small program to log on is:
Failure to find a user who is bound by the openid of the eprogram jumps to the login page, asks the user to enter the user name (mailbox or phone) and password, and then binds the user to the e-program openid, returning to access-token, and the login is successful. You can find the bound user based on the openid of the esmalle, return directly to access-token, and log on successfully.


laravel sms api

Configure Content

Non-template channels that can be customized via config/ibrand/sms.php ‘content’ and ‘you signature Dear user, your verification code is %s. Valid for %s minutes, please verify as soon as possible.


In real-world development there is a situation where a verification code is not actually issued, so in debug mode, you can

http://your.domain/api/sms/info?mobile=1898888XXXX to look directly at the current valid verification code information for a cell phone number.
database log

Support is now being supported for saving the send record to the database and performing the php artisan migrate to generate the laravel?sms-log table. Set dblog to true at config/ibrand/sms.php at the same time


Laravel easy sms

Extended development based on business requirements in overtrue/easy-sms, primarily for the following:
Support sMS verification codes to configure template Ids directly in config
Support sMS verification code customization length
Support for SMS verification code valid minutes, default 5 minutes
Support sMS verification code retry times to prevent users from accidentally mis-sending verification code caused by the need to send the verification code again
When the support SMS verification code is not verified, the user requests the verification code again, which is consistent within a valid minute
Integrated SMS sending routing to support web and api delivery methods
Support for verification code debugging, debug mode can directly query the mobile phone number is currently valid verification code, debug mode will not verify the correctness of the verification code Supports verification codes to send records to the database for easy viewing of send logs and error causes