Home  >  Article  >  Backend Development  >  laravel 5.3 passport encounters some pitfalls

laravel 5.3 passport encounters some pitfalls

WBOY
WBOYOriginal
2016-12-01 00:25:471305browse

http://laravelacademy.org/pos...

Using the documentation to build it step by step to the third step

laravel 5.3 passport encounters some pitfalls
Then something went wrong here

laravel 5.3 passport encounters some pitfalls

This is a pitfall, and I haven’t been able to find a solution. It has been solved. It turns out that after logging in with auth, the vue component is placed in home.blade.php

https://laravel-china.org/top...
Then I found this tutorial. When the route jumps below, the program responsible for the api jumps directly to the login route, and then checks the route list to find the API interface. They all use auth middleware. I followed the tutorial documents step by step. Why is this happening? . .

laravel 5.3 passport encounters some pitfalls

laravel 5.3 passport encounters some pitfalls

Reply content:

http://laravelacademy.org/pos...

Using the documentation to build it step by step to the third step

laravel 5.3 passport encounters some pitfalls
Then something went wrong here

laravel 5.3 passport encounters some pitfalls

This is a pitfall, and I haven’t been able to find a solution. It has been solved. It turns out that after logging in with auth, the vue component is placed in home.blade.php

https://laravel-china.org/top...
Then I found this tutorial. When the route jumps below, the program responsible for the api jumps directly to the login route, and then checks the route list to find the API interface. They all use auth middleware. I followed the tutorial documents step by step. Why is this happening? . .

laravel 5.3 passport encounters some pitfalls

laravel 5.3 passport encounters some pitfalls

Can you try using the private token directly to see if you can access the interface?
I also accessed the api and jumped to the login page...

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn