We have been working on this project for half a year. There was no problem before. Since last Saturday, all interfaces have been prompted
:
laravel5.5return view()iview-adminnodelaravelapi.php ;;oAuth
bladephp
:
.
error details
"exceptions": {
"count": 1,
"exceptions": [
{
"type": "Illuminate\\Auth\\AuthenticationException",
"message": "Unauthenticated.",
"code": 0,
"file": "D:\\jeff\\code\\jianwen\\vendor\\laravel\\framework\\src\\Illuminate\\Auth\\Middleware\\Authenticate.php",
"line": 66,
"surrounding_lines": [
" }\n",
" }\n",
"\n",
" throw new AuthenticationException("Unauthenticated.", $guards);\n",
" }\n",
"}\n"
],
"xdebug_link": null
}
]
},
to meet the needs of the respondent, post the auth code
<?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" => "web",
"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" => [
// jhc
"driver" => "passport",
"provider" => "users",
],
],
/*
|--------------------------------------------------------------------------
| JUser 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\Models\User::class,//jhc
],
// "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,
],
],
// jhc
"agent" => [
"agent_id" => env("AUTH_AGENT_ID", ""),
"redirect_url" => env("AUTH_REDIRECT_URL", ""),
"platform_url" => env("AUTH_PALTFORM_URL", ""),
"gateway_url" => env("AUTH_GATEWAY_URL", ""),
"corp_user_api" => "auth_user",
"corp_token_api" => "corp_tokens",
"corp_info" => "auth_corp",
"token" => env("AUTH_TOKEN", ""),
"encoding_key" => env("AUTH_ENCODING_KEY", "")
],
];