1,200 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.
If the client is a web application that has a server side component then you should implement the authorization code grant.
Which is exactly the way I was thinking, so I feel validated.
I think what will work is to create a client "manually" that isn't associated with a user and follows the authorization code grant flow. I can manage the clients via Nova using a "super admin" role or something.
Thanks for bringing up the docs, they were indeed worth a read.
Started a new Conversation Using Passport To Authenticate Other Applications
Apologies, as I know this question has probably been asked before but can't seem to find the answers I'm looking for.
Our org uses AD to manage users and authentication. I have several internal "microservices" or other applications but don't want to add AD integrations to all of them as it's a headache.
I want to use a single application as the authentication server that interfaces with AD (already set up and working) but acts as an OAuth server to the users to use other internal applications. I have Laravel Passport installed on this central "user" application.
Essentially, I'm wanting my own "Log in with Google" functionality, only with the central user application. The terminology is confusing to me on which type of client I need to create for Passport. Are my other applications considered "first-party" clients? It doesn't make sense to create a client for a specific user, as it's going to be used for all my users.
What would the flow be for these internal applications? Again, this is probably answered somewhere else, I just can't seem to find it!
Replied to How To Cache Laravel Passport Auth Calls
Also have this same question. My api is limited to very few users and changes very rarely. Would love to be able to cache these requests to squeeze as much performance as I can...