2,550 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Earned once your experience points ranks in the top 10 of all Laracasts users.
Started a new Conversation Password + Passwordless Login In One Application
So I am building an application for a client who manages events that are staffed by volunteers from local non-profit organizations. There are four user roles (volunteer, organization manager, stand manager, and administrator) in the system of which one user can belong to many. I am using the spatie/laravel-permission package to manage these.
The challenge that I'm facing is that I would like to require a different method of authentication based on the user's role. More specifically:
I would like to authenticate users with the "volunteer" role attempting to access volunteer related content via a password-less email link using the grosv/laravel-passwordless-login package.
Whereas, I would like to authenticate users with the "organization manager", "stand manager", and "administrator" roles attempting to access their role's respective content via email and password using the Laravel Fortify package.
The reasoning behind this request from the client is to reduce the friction of the volunteer registration process, as their current system requires users to create an account to register, resulting in reduced registration completion rates and issues with returning volunteers forgetting their passwords and having to go through the trouble of resetting it.
While I have contemplated creating a dedicated Volunteer model separate from the User model, I feel this would only be pushing the issue to another part of the application rather than truly resolving it.
My current thoughts are as follows:
As the majority of users will be volunteers who do not require a password, extract the password column to its own table to avoid making the password column nullable.
When a user with a role that requires a password attempts to access content for their respective role, authenticate them (via a guard or middleware?) and require them to set a password if one does not already exist for their user account.
I'm lost however as to how I should manage the authentication state for the different authentication methods. For example, if a user has been accessing volunteer specific content that has only required them to authenticate via the password-less method and then attempts to access say administrator content that requires a password, how do I differentiate between the two "levels" of authentication?
All help that can be offered is greatly appreciated. Thanks!