Member Since 4 Years Ago
530 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.
Just to close this out... I couldn't resolve the error so I abandoned Sanctum and went with Passport. No issues at all getting passport running with password grant tokens and personal access tokens.
Thanks for the suggestions, but I'm 100% certain the
APP_KEY and encryption method have not been changed. This is a fresh (today) install that has only had the original key in the .env and the cipher is still
AES-256-CBC as set in the app config.
I did try clearing the application and browser caches as well as tried different browsers to be certain and no luck still.
I've also done an additional fresh install since posting this and received the the same results unfortunately.
Started a new Conversation DecriptionException: The MAC Is Invalid - Laravel Sanctum
I've got a fresh install of Laravel 7.1 with Sanctum 2.0 running at api.domain.test and a fresh install of a Vue CLI frontend at app.domain.test.
I'm able to retrieve the CSRF cookie from the
/sanctum/csrf-cookie route and Axios is setting the
X-XSRF-TOKEN header when making a request to the
/login route, but the
VerifyCsrfToken middleware is throwing a
DecriptionException stating that the MAC is invalid.
I tested the app's ability to encrypt and decrypt via Tinker, which works as expected. I didn't find much searching.
This seems to be a common issue when people are swapping the
APP_KEY, after encrypting data, but that isn't the issue here.
Any suggestions on what I should be looking for here?