laravel-email-verification | Easily add email verification to your Laravel
kandi X-RAY | laravel-email-verification Summary
kandi X-RAY | laravel-email-verification Summary
laravel-email-verification is a PHP library. laravel-email-verification has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.
Easily add email verification to your web project or API.
Easily add email verification to your web project or API.
Support
Quality
Security
License
Reuse
Support
laravel-email-verification has a low active ecosystem.
It has 0 star(s) with 0 fork(s). There are 1 watchers for this library.
It had no major release in the last 12 months.
laravel-email-verification has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of laravel-email-verification is v1.1.1
Quality
laravel-email-verification has no bugs reported.
Security
laravel-email-verification has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
laravel-email-verification is licensed under the MIT License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
laravel-email-verification releases are available to install and integrate.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of laravel-email-verification
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of laravel-email-verification
laravel-email-verification Key Features
No Key Features are available at this moment for laravel-email-verification.
laravel-email-verification Examples and Code Snippets
No Code Snippets are available at this moment for laravel-email-verification.
Community Discussions
No Community Discussions are available at this moment for laravel-email-verification.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install laravel-email-verification
Install the package using composer:
Laravel has package auto-discovery since version 5.5. If you have an older version, register the service provider in config/app.php:
Run the migration to install the package's table to manage verification tokens:
Add the package's trait EmailVerifiable to your User model to add helper methods to it, namely the verificationToken() relationship and a method to check if the user's email has been verified emailVerified().
Further steps for a regular web project. Skip this section if you're developing an API. The registered() method generates a token for a newly registered user, emails it to them, logs the user out, and redirects them to the login page with a message. More on this later. You can also register this middleware as a route middleware to apply it to selected routes and not the whole web middleware group.
Override the registered method on the RegisterController file. Call the package's registered() method inside.
Register the package's middleware which logs out and redirect to the login page all authenticated users with unverified emails. You can do this in the app/Http/Kernel.php file like this.
Further steps for an API project. Skip this section if you're developing a regular web project. The registeredApi() method generates a token for a newly registered user, emails it to them, and returns a JSON response. You can also register this middleware as a route middleware to apply it to selected routes and not the whole api middleware group. The package provides a GET endpoint /api/auth/email-verification/{token} in case you want to handle the verification in some different way. It tries to verify the provided in the URL token and returns a JSON response with a message and a 200 status (in case the token is correct) or 404 status (if the token does not exists or is expired).
Call this method after you've registered a user in your API.
Register the package's middleware which logs out all the authenticated users with unverified emails and returns a JSON response with a 409 status code. You can do this in the app/Http/Kernel.php file like this.
The email verification link sent in the email will point to whatever domain the API is located at, even if you're using a web client on a different domain, or say a mobile client.
Laravel has package auto-discovery since version 5.5. If you have an older version, register the service provider in config/app.php:
Run the migration to install the package's table to manage verification tokens:
Add the package's trait EmailVerifiable to your User model to add helper methods to it, namely the verificationToken() relationship and a method to check if the user's email has been verified emailVerified().
Further steps for a regular web project. Skip this section if you're developing an API. The registered() method generates a token for a newly registered user, emails it to them, logs the user out, and redirects them to the login page with a message. More on this later. You can also register this middleware as a route middleware to apply it to selected routes and not the whole web middleware group.
Override the registered method on the RegisterController file. Call the package's registered() method inside.
Register the package's middleware which logs out and redirect to the login page all authenticated users with unverified emails. You can do this in the app/Http/Kernel.php file like this.
Further steps for an API project. Skip this section if you're developing a regular web project. The registeredApi() method generates a token for a newly registered user, emails it to them, and returns a JSON response. You can also register this middleware as a route middleware to apply it to selected routes and not the whole api middleware group. The package provides a GET endpoint /api/auth/email-verification/{token} in case you want to handle the verification in some different way. It tries to verify the provided in the URL token and returns a JSON response with a message and a 200 status (in case the token is correct) or 404 status (if the token does not exists or is expired).
Call this method after you've registered a user in your API.
Register the package's middleware which logs out all the authenticated users with unverified emails and returns a JSON response with a 409 status code. You can do this in the app/Http/Kernel.php file like this.
The email verification link sent in the email will point to whatever domain the API is located at, even if you're using a web client on a different domain, or say a mobile client.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page