jwt-auth: Can't get token with Laravel 6.0 and jwt-auth 1.0.0-rc.5 when trying to authenticate

Token value is always false

Hello. I used jwt-auth 1.0.0-rc.5 to handle authentication with laravel 6.0. My AuthController code is pasted below.

When registering a new user with the method register in AuthController, I succesfully get a jwt token.

But when trying to athenticate the user I created earlier, token value is always false

`<?php

namespace App\Http\Controllers;

use DB; use Hash; use App\User; use App\RoleUser; use Illuminate\Http\Request;

class AuthController extends Controller { public function authenticate(Request $request) { $credentials = $request->only(‘email’, ‘password’);

	$token = auth()->attempt($credentials);

    // var_dump(Hash::make($credentials['password']));
    // var_dump($token);
    
	if($token)
		return $token;
	return response()->json(['error' => 'Unauthorized'], 401);
}

public function register(Request $request)
{

    $request->validate([
        'role'      =>  'required',
        'email'     =>  'required|unique:users',
        'password'  =>  'required',
        'firstname' =>  'required',
        'lastname'  =>  'required'
    ],[
        'role'          => 'Le niveau de role est requis',
        'email.unique'  => "L'adresse email est requise",
        'password'      => 'Le mot de passe est requis',
        'firstname'     => 'Le prénom est requis',
        'lastname'      => 'Le nom de famille est requis'
    ]);

    DB::beginTransaction();

        $user = User::create([
         'email'        => $request->email,
         'password'     => $request->password,
         'firstname'    => $request->firstname,
         'lastname'     => $request->lastname
        ]);

        RoleUser::create([
            'role_name' => $request->role,
            'user_id'  => $user->id
        ]);

    DB::commit();

    $token = auth()->login($user);

    // var_dump($token);

    return $this->respondWithToken($token);
}

 protected function respondWithToken($token)
{
    return response()->json([
        'access_token' => $token,
        'token_type'   => 'bearer',
        'expires_in'   => auth()->factory()->getTTL() * 60
    ]);
}

} `

`<?php

return [

/*
|--------------------------------------------------------------------------
| Authentication Defaults
|--------------------------------------------------------------------------
|
| This option controls the default authentication "guard" and password
| reset options for your application. You may change these defaults
| as required, but they're a perfect start for most applications.
|
*/

'defaults' => [
    'guard' => 'api',
    'passwords' => 'users',
],

/*
|--------------------------------------------------------------------------
| Authentication Guards
|--------------------------------------------------------------------------
|
| Next, you may define every authentication guard for your application.
| Of course, a great default configuration has been defined for you
| here which uses session storage and the Eloquent user provider.
|
| All authentication drivers have a user provider. This defines how the
| users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user's data.
|
| Supported: "session", "token"
|
*/

'guards' => [
    'web' => [
        'driver' => 'session',
        'provider' => 'users',
    ],

    'api' => [
        'driver' => 'jwt',
        'provider' => 'users',
        'hash' => false,
    ],
],

/*
|--------------------------------------------------------------------------
| User Providers
|--------------------------------------------------------------------------
|
| All authentication drivers have a user provider. This defines how the
| users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user's data.
|
| If you have multiple user tables or models you may configure multiple
| sources which represent each model / table. These sources may then
| be assigned to any extra authentication guards you have defined.
|
| Supported: "database", "eloquent"
|
*/

'providers' => [
    'users' => [
        'driver' => 'eloquent',
        'model' => App\User::class,
    ],

    // 'users' => [
    //     'driver' => 'database',
    //     'table' => 'users',
    // ],
],

/*
|--------------------------------------------------------------------------
| Resetting Passwords
|--------------------------------------------------------------------------
|
| You may specify multiple password reset configurations if you have more
| than one user table or model in the application and you want to have
| separate password reset settings based on the specific user types.
|
| The expire time is the number of minutes that the reset token should be
| considered valid. This security feature keeps tokens short-lived so
| they have less time to be guessed. You may change this as needed.
|
*/

'passwords' => [
    'users' => [
        'provider' => 'users',
        'table' => 'password_resets',
        'expire' => 60,
    ],
],

]; `

About this issue

  • Original URL
  • State: open
  • Created 5 years ago
  • Reactions: 2
  • Comments: 30

Most upvoted comments

@I2C-RoyYou Hi,i has been sloved this problem. You can read the wiki from https://github.com/tymondesigns/jwt-auth/wiki/Authentication

It tell us , when you login by the api middleware(jwt), and then, if you want to refresh the user’s token,you need to parsed the user’s token in request headers or in input request params firstly.

LOOK AT THIS:

// this will set the token on the object
JWTAuth::parseToken();

// and you can continue to chain methods
$user = JWTAuth::parseToken()->authenticate();

DO NOT READ THE https://jwt-auth.readthedocs.io/en/develop/auth-guard/, IT CAN NOT TELL US ABOUT DEFAULT GUARD WHICH IS NOT api

MY CODE, MAY BE HELPFUL TO U:


    public function login(Request $request)
    {
        $credentials = $request->only('username', 'password');

        try {
            if (!$token = JWTAuth::attempt($credentials)) {
                return response()->json(['error' => 'invalid_credentials'], 401);
            }

            return response()->json(['data' => $this->makeToken($token)]);
        } catch (JWTException $e) {
            return response()->json(['error' => Str::slug($e->getMessage(), '_')], 500);
        }
    }

    
    public function logout(Request $request)
    {
        auth('api')->logout();

        return response()->json(['message' => 'logout_success']);
    }

    
    public function refresh(Request $request)
    {
        try {
            return response()->json(['data' => $this->makeToken(JWTAuth::parseToken()->refresh())]);
        } catch (JWTException $e) {
            info($e);

            return response()->json(['error' => Str::slug($e->getMessage(), '_')], 401);
        }
    }

    
    public function me(Request $request)
    {
        try {
            return response()->json(['data' => JWTAuth::parseToken()->authenticate()]);
        } catch (JWTException $e) {
            info($e);

            return response()->json(['error' => Str::slug($e->getMessage(), '_')], 401);
        }
    }

protected function makeToken($token)
    {
        return [
            'access_token' => $token,
            'token_type'   => 'bearer',
            'expires_in'   => JWTAuth::factory()->getTTL() * 60
        ];
    }

IMPORTANT : JWTAuth::parseToken()->refresh()

now, you can put the header parma Authorization: bearer {user's token} for refresh user’s token from your client

I got the same problem too, can’t figure the problem out. I have tested the 1.0.0.rc5.1 and still doesn’t work for me. What I do is I just followed this tutorial EXACTLY with new laravel project (6.13) but the problem still persists. Does the problem is because of my OS (Windows?), or because the XAMPP? Tutorial Link

have you try this? I use this and success auth!

change token position, put it to url parameters. like doc says , use http://<your api url>?token=<your token> , and cancel bearar auth