laravel-authentication

问题 I have two Guards Admin User Also i have created controllers where user can manage his own data and admin can also manage user data. So i created two Controllers Controllers Admin EducatonBackgroundController User EducationBackgroundController In User/EducationBackgroundController i have this function which fetch education background of a current logged user and display on the user view public function index(Education $education) { try { $educations = $education->where('user_id',$this-

来源： https://stackoverflow.com/questions/55626323/changing-laravel-auth-table-name-and-column-names

问题 I have a Laravel 6 application. In a typical application, the user would just specify their email , where the email is unique. However, in my application, I have 2 columns in the User model that is used to authenticate users. app_id email unique(app_id, email) So in order to login, we need to pass both an app_id and an email , along with the password . The same email could be used across different app_id s. How would I achieve this? 回答1: The default login actions provided by Auth::routes()

问题 I have a Laravel 6 application. In a typical application, the user would just specify their email , where the email is unique. However, in my application, I have 2 columns in the User model that is used to authenticate users. app_id email unique(app_id, email) So in order to login, we need to pass both an app_id and an email , along with the password . The same email could be used across different app_id s. How would I achieve this? 回答1: The default login actions provided by Auth::routes()

问题 I have created four user type admin,vendor,employee,customer . In the user migration file I have the following: public function up() { Schema::create('users', function (Blueprint $table) { $table->bigIncrements('id'); $table->string('name'); $table->string('email')->unique(); $table->char('contact',24)->nullable(); $table->string('password'); $table->enum('roles',['admin', 'vendor', 'employee', 'customers']); $table->string('image')->nullable(); $table->timestamps(); }); } I have already

问题 I have created four user type admin,vendor,employee,customer . In the user migration file I have the following: public function up() { Schema::create('users', function (Blueprint $table) { $table->bigIncrements('id'); $table->string('name'); $table->string('email')->unique(); $table->char('contact',24)->nullable(); $table->string('password'); $table->enum('roles',['admin', 'vendor', 'employee', 'customers']); $table->string('image')->nullable(); $table->timestamps(); }); } I have already

问题 I have created four user type admin,vendor,employee,customer . In the user migration file I have the following: public function up() { Schema::create('users', function (Blueprint $table) { $table->bigIncrements('id'); $table->string('name'); $table->string('email')->unique(); $table->char('contact',24)->nullable(); $table->string('password'); $table->enum('roles',['admin', 'vendor', 'employee', 'customers']); $table->string('image')->nullable(); $table->timestamps(); }); } I have already

问题 I have a multiauth laravel 5.2 app, with the fallowing guards defined on config/auth.php : ... 'admin' => [ 'driver' => 'session', 'provider' => 'admin', ], 'user' => [ 'driver' => 'session', 'provider' => 'user', ], ... So, admin and user . The problem resides in the view layer, since this two loggedin guards share some views, ex: Hello {{Auth::guard('admin')->user()->name}} In this case the guard is hardcoded into the view to be always admin (it gives error when loggedin guard is user ),

问题 I have two tables: persons: id name email phone person_type_id users id person_id password role_id etc... Could you please tell me how to make Laravel's (5.8) built in Authentication System use the email field from persons table when authenticating a user? FYI, the value of guard provider has to be users . 回答1: You could create a custom user provider (which inherits from Illuminate\Auth\EloquentUserProvider ) and override the retrieveByCredentials method. See Laravel Docs - The User Provider

问题 The default behaviour of Laravel (5.7)'s password reset system is to create a new token in the password_resets table after deleting any others for that user. This behaviour is determined in \Illuminate\Auth\Passwords\DatabaseTokenRepository and it doesn't seem configurable. protected function deleteExisting(CanResetPasswordContract $user) { return $this->getTable()->where('email', $user->getEmailForPasswordReset())->delete(); } There's so much inheritance going on, I can't figure out what