JSON API: The route oauth\/token could not be found

[mrmedia]

After my own upgrade on the whole package I still have a problem to put the JSON API (PRO) into operation:

It permanently says

{"jsonapi":{"version":"1.0"},"errors":[{"detail":"The route oauth\/token could not be found.","status":"400","title":"Bad Request"}]}

Even if I fire the request with my own client and the bearer from https://documenter.getpostman.com/view/8138626/T1DiFzku#jsonapi
the API response are still the same.

POST /api/v2/login HTTP/1.1
Host: localhost:8000
Accept: application/vnd.api+json
Content-Type: application/vnd.api+json
authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiIyIiwianRpIjoiNjNmZjk2ODUxMGE2YzQ1MjJlYWNlMTUyN2I5YzE4Y2RiYWUwMjY5MmVjOGFkMjM2YWE5ZWFhMjcwYjVlODYzMzZjY2ViODI1NmRjZmNiOTgiLCJpYXQiOjE1ODY5NTYzODksIm5iZiI6MTU4Njk1NjM4OSwiZXhwIjoxNjE4NDkyMzg5LCJzdWIiOiIxIiwic2NvcGVzIjpbXX0.Wg6y5GlkOzzeotv0sKIz2qGitNo5C4Niky3bzfIYa6amg0LabM8EHt7pZAklE-eJa0b4UY0-vag1WQuQJFDmoMzEMQfZcIZoTdty5-sGVvzy81RZfnN__i7Bd7VSDFevFHJRvvSn3QG-0woqBTFxd14Hwj6GjwWiDtnJtOtrQ3ylFvQ98zOz0LxcnU3FKALXx8loTO_ttIUcLZffHGmD6TsxAH0v70QSnDNVtcYmY30j7TCjcltuAVaeq3ZFcLQ2R4tvpAfPr-CFjvhWp59JS9qM_wgOA-WNlYIB5buxWEMDDcgK3q2sWgCzNGmEgtpa-EU3WLn-ifzOOh7XrBXpJXdNyQo7mYNzjU6jDnER-ksQ3V8DcpYf0oC2nrfrsOdfr02F1FboSRhuuSGa-yZE-t4urkgp5GkRNSyDde-cVyLwvo_PMnFC_zcANbO5C2K2Kb6WHv4y7zk8aqNmT3eAQMdZK5jMCf3nryjF5X-bTxZRRCmEOBcUG23AZap9UP6Rduwq2sUFqFT9BIJaBTQPkpHAFdbyusZntrKS1C8AKNgvdqM5NVzeZrEyPDJRkVsG7_yb8u53Ad6jEyhOWGte4vqACbDgAdMp2qQbQN9Rk0LjgjIvrFMg2nkivyT_HPq0VFIzz8bzuvCxkPcJS9eNF6ZqnigiVIKreAuCT3XC7yg

{
    "data": {
        "type": "token",
        "attributes": {
            "email": "[admin@jsonapi.com](mailto:admin@jsonapi.com)",
            "password": "secret"
        }
    }
}

Do you have any hint for me what I’m doing wrong?
If I fire the call to creative-tim’s API the response is fine! So surely something is missing on my side?

[teamupdivision]

Hello,

Thank you for using Creative Tim products!
Since you did the upgrade by yourself it is a bit difficult to know exactly where the issue may be. Maybe this can help --> https://laracasts.com/discuss/channels/laravel/laravel-passport-post-oauthtoken-resulted-in-a-404-not-found

You do not need to send header for auth login. Also please make sure that you have the client setup for passport and that client_id and client_secret are set correctly in the env.

Also did you make sure to follow all the correct steps when installing the API?

[mrmedia]

Hi,

yes, followed the instructions multiple times.

I had to update the package on myself because it were not running on my machine, the downloaded build is completely outdated (we have discussed this per email together)

I've also tried to install different downloads from my 400$ Club Membership, none of them is running out of the box. They're all not up to date.

I've just updated the packages to get it running with babel/eslint-parser instead of babel-eslint and modified the .vue files to get rid of the errors like multiple-word-guideline and reserved HTML Names like "Form". The API Project itself is running, and the frontend is running now also. Except for the above posted error while trying to hit the login button.

Would be glad if you were able to start a RD session to help me out with that little problem - I think you know you're software the best I guess.

Thank you!

[mrmedia]

Hi, I figured out that the trailing / at the end of APP_URL in .env of API was a problem?

But now I'm running into this closed topic:
creativetimofficial/vue-now-ui-dashboard-laravel#2

[mrmedia]

VUE SETUP

VUE_APP_BASE_URL=http://localhost:8080/
VUE_APP_API_BASE_URL=http://localhost:8000/api/v2/

IF i set in API
APP_URL=http://127.0.0.1:8000

and let

$request = Request::create(config('app.url') . '/oauth/token', 'POST', [...

untouched, I get following response:

{
  "jsonapi": {
    "version": "1.0"
  },
  "errors": [
    {
      "detail": "The route oauth/token could not be found.",
      "status": "400",
      "title": "Bad Request"
    }
  ]
}

If I change APP_URL to trailing slash

APP_URL=http://127.0.0.1:8000/

and remove the trailing slash from

$request = Request::create(config('app.url') . 'oauth/token', 'POST', [...

I receive follow answer from the API

{
  "token_type": "Bearer",
  "expires_in": 86400,
  "access_token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiIyIiwianRpIjoiODE5NzRlY2VjMGI3YWU3M2QxM2I3ODk5OGEyMmE4YzM5N2Q1OGQ4ZjhjNjI1MDcyNzk2ZDUwZjA1M2I3MTc0Yjg0OGVjYmViOWExNmQ1NzEiLCJpYXQiOjE2ODk5MzExNzEuMDM5Njc0LCJuYmYiOjE2ODk5MzExNzEuMDM5Njc1LCJleHAiOjE2OTAwMTc1NzEuMDMxNTksInN1YiI6IjEiLCJzY29wZXMiOltdfQ.GQ9sxDTP_BfxUa6ESJyjo8vpsbabgWThTkakFwx93ZetN0FPc4HQzL6tazqQgkV7hQKpgfMqYsdbINnRtoSxNmfHj-aYQwquaNDF0BAus3c7cZ2Yki27g3T_Mz2Y_UuF9wD-7XWUj2bzAtm0nH9D0gDNUdUrbgT51O9tVI6-SE6CwtdkAFbZkFwRDgsCyNK41qsUA9HgI01tkKWG7ifSREIMPFMjHyi6OtgsXuDdncHbxPZIOFv3LkmYC-NXdVuRrMMfWg0OVzw07auYzczT3kZhr_8RCtEeC315okcIXTwuqe9QQgDSnPBIteCsFQTJFrmyRDXrKpF1cTqVfD5aWbuEYCi9OQLYCX4a6ns1e7u7ODB_RzqKwMJeWUZiiA3HNqwhtxSU2KS_swVWVNSaTTbTVwyXeHUXwMG0Z3O0KQQrpakVi7GdnB-PT1zw7h8C7GA7Eic1zSHuWcUZVUR2BY4GsvLl5twXYVx4SjSIj0S_9SBRibeUQ9PPmzAC-ykPZaJ8EKqOnqDUuddx-Q_N0Db7RxfCdUa3oWFq2UO9dW2tJBui6vaOSIDyx4LsMChzB8cK0fgFh5ioE2kfbnPbjFyWfUV0WJdaIcIwtARCdPZX63xhy6cTXgenGBU-oJGlgE6I5SzT2oRxh6881aAXjfAUdpx_tWY_PJbnSHzPzyU",
  "refresh_token": "def502006572349c9ed5ed961024fcf877047793ec05085a25ea381f2c7a5a203a126614dc5069bd591a01143bbf49dbc64fb83e863c5577cc944043ab3f8303c57685e2d4d1d7583e68fa86c6f13b78031b09c0a44b920f802cdbfeeb936db2e4c72b9b8bf378cd95f1296cf92c7c1480f98bbec0c80a092f9d0e10b9b5ae5bef40983822360755dbb7c27ccc3d06ec2da5b2211fb78f8d13cd49f26fb5da91ee704b83bcab8a66d78fc6fb58409fbf714756dec6b710ead36f950de5d3f807d9e5d31bde551606b1358d16fd4e740d10d7d3eb49c9cc29ce4ea3b5f75bc9af15d09db16f4d1e2a911c2f9c048201b051ab9b95a3541c0156d13e3801c0f93c6a0fe1c5db8578cc2d4e509f660c35b3bc257bf50eb9fe5ca2d0549ec5cea092f8ff499c3d98d0f2af9b39658eb2dc05afa15edd3dcd7a6ba6c0addfb46decfd37f756d862e551a397a1c03203a7a298b2d23a10b49dd4cee10cfe3dda927f013c"
}
    

THIS running, a user is written to local browser storage, BUT the API is freezing with the next request.

http://127.0.0.1:8000/api/v2/me?include=roles

Important now to kill the frozen process each time so the API is able to receive a new request.

Backtrace to:

/laravel-json-api-pro/app/Http/Controllers/Api/V2/MeController.php : 42

        try {

            $response = $http->get(route('v2.users.show', ['user' => auth()->id()]), $data);

[mrmedia]

print var_dump(route('v2.users.show', ['user' => auth()->id()]));
=>
string(36) "http://127.0.0.1:8000/api/v2/users/1"

Works via own REST Client, hangs via Guzzle. Why?

[TokiTunes]

I have the EXACT same issue as @mrmedia and paying for premium, I would like to see a resolution for this. Time is money, and I paid you guys to save time, now I'm losing that paid for time because you guys aren't holding up to your end of the bargain and providing a completed functioning product.

[TokiTunes]

Seeing as you guys are having a hard time figuring out whats wrong. How about you go to your own live demo, this is behaving the exact same way as mine.... https://vue-soft-ui-dashboard-pro-laravel.creative-tim.com

You fix that, it should fix ours.

[teamupdivision]

Hello,

sorry for delayed response.

We just pushed a fix on github that should fix the issue.

Please let us know if it works now.

[TokiTunes]

@mrmedia you get a much faster response if you go to the company discord... https://discord.gg/vf3EB6Bh

I went there and within a day, they updated it :)