laravel修改用戶模塊的密碼驗證實現(xiàn)
做項目的時候,用戶認證幾乎是必不可少的,如果我們的項目由于一些原因不得不使用 users 之外的用戶表進行認證,那么就需要多做一點工作來完成這個功能。
現(xiàn)在假設我們只需要修改登錄用戶的表,表名和表結(jié)構(gòu)都與框架默認的表users不同,文檔沒有教我們?nèi)绾稳プ觯莿e慌,稍微看下框架實現(xiàn)用戶認證的源碼就能輕松實現(xiàn)。
首先,自定義一張表用來登錄,表結(jié)構(gòu)和模擬數(shù)據(jù)如下:
表 admins
id | login_name | login_pass |
---|---|---|
1 | admin | 10$2MUhp7b6ghVOngb/.b/x6uuEW/yL3FqPKJztawrM0U577Clf07xda |
從配置文件入手
用戶認證相關的配置都保存在config/auth.php文件中,先來看看配置文件的內(nèi)容:
<?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' => [ 'driver' => 'passport', 'provider' => 'users', ], ], /* |-------------------------------------------------------------------------- | 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, ], ], ];
默認使用的守衛(wèi)是web,而web守衛(wèi)使用的認證驅(qū)動是session,用戶提供器是users。假設我們的需求只是將用戶的提供器由users改為admins,那么我們需要做兩步操作:
修改默認的用戶提供器,將provider=>'users'改為provider=>'admins'
'guards' => [ 'web' => [ 'driver' => 'session', 'provider' => 'users', ], ],
配置admins提供器,假設依舊使用eloquent作為驅(qū)動,并創(chuàng)建好了admins表的模型
'providers' => [ 'admins' => [ 'driver' => 'eloquent', 'model' => App\Admin::class ] ],
使用Auth門面的attempt方法進行登錄
SessionGuard 中的attempt方法:
//Illuminate\Auth\SessionGuard public function attempt(array $credentials = [], $remember = false) { $this->fireAttemptEvent($credentials, $remember); $this->lastAttempted = $user = $this->provider->retrieveByCredentials($credentials); // If an implementation of UserInterface was returned, we'll ask the provider // to validate the user against the given credentials, and if they are in // fact valid we'll log the users into the application and return true. if ($this->hasValidCredentials($user, $credentials)) { $this->login($user, $remember); return true; } // If the authentication attempt fails we will fire an event so that the user // may be notified of any suspicious attempts to access their account from // an unrecognized user. A developer may listen to this event as needed. $this->fireFailedEvent($user, $credentials); return false; }
該方法中調(diào)用 UserProvider 接口的retrieveByCredentials方法檢索用戶,根據(jù)我們的配置,UserProvider接口的具體實現(xiàn)應該是EloquentUserProvider,因此,我們定位到EloquentUserProvider的retrieveByCredentials方法:
//Illuminate\Auth\EloquentUserProvider public function retrieveByCredentials(array $credentials) { if (empty($credentials) || (count($credentials) === 1 && array_key_exists('password', $credentials))) { return; } // First we will add each credential element to the query as a where clause. // Then we can execute the query and, if we found a user, return it in a // Eloquent User "model" that will be utilized by the Guard instances. $query = $this->createModel()->newQuery(); foreach ($credentials as $key => $value) { if (Str::contains($key, 'password')) { continue; } if (is_array($value) || $value instanceof Arrayable) { $query->whereIn($key, $value); } else { $query->where($key, $value); } } return $query->first(); }
該方法會使用傳入的參數(shù)(不包含password)到我們配置的數(shù)據(jù)表中搜索數(shù)據(jù),查詢到符合條件的數(shù)據(jù)之后返回對應的用戶信息,然后attempt方法會進行密碼校驗,校驗密碼的方法為:
//Illuminate\Auth\SessionGuard /** * Determine if the user matches the credentials. * * @param mixed $user * @param array $credentials * @return bool */ protected function hasValidCredentials($user, $credentials) { return ! is_null($user) && $this->provider->validateCredentials($user, $credentials); }
進一步查看EloquentUserProvider中的validateCredentials方法
//Illuminate\Auth\EloquentUserProvider public function validateCredentials(UserContract $user, array $credentials) { $plain = $credentials['password']; return $this->hasher->check($plain, $user->getAuthPassword()); }
通過validateCredentials可以看出,提交的認證數(shù)據(jù)中密碼字段名必須是password,這個無法自定義。同時可以看到,入?yún)?user必須實現(xiàn)Illuminate\Contracts\Auth\Authenticatable接口(UserContract是別名)。
修改 Admin 模型
Admin模型必須實現(xiàn)Illuminate\Contracts\Auth\Authenticatable接口,可以借鑒一下User模型,讓Admin直接繼承Illuminate\Foundation\Auth\User 就可以,然后重寫getAuthPassword方法,正確獲取密碼字段:
// App\Admin public function getAuthPassword() { return $this->login_pass; }
不出意外的話,這個時候就能使用admins表進行登錄了。
Larval 5.4的默認Auth登陸傳入郵件和用戶密碼到attempt 方法來認證,通過email 的值獲取,如果用戶被找到,經(jīng)哈希運算后存儲在數(shù)據(jù)中的password將會和傳遞過來的經(jīng)哈希運算處理的passwrod值進行比較。如果兩個經(jīng)哈希運算的密碼相匹配那么將會為這個用戶開啟一個認證Session。
參考上面的分析,我們就需要對EloquentUserProvider中的validateCredentials方法進行重寫,步驟如下
1. 修改 App\Models\User.php 添加如下代碼
public function getAuthPassword() { return ['password' => $this->attributes['password'], 'salt' => $this->attributes['salt']]; }
2. 建立一個自己的UserProvider.php 的實現(xiàn)
<?php namespace App\Foundation\Auth; use Illuminate\Auth\EloquentUserProvider; use Illuminate\Contracts\Auth\Authenticatable; use Illuminate\Support\Str; /** * 重寫用戶密碼校驗邏輯 * Class GfzxEloquentUserProvider * @package App\Foundation\Auth */ class GfzxEloquentUserProvider extends EloquentUserProvider { /** * Validate a user against the given credentials. * * @param \Illuminate\Contracts\Auth\Authenticatable $user * @param array $credentials * @return bool */ public function validateCredentials(Authenticatable $user, array $credentials) { $plain = $credentials['password']; $authPassword = $user->getAuthPassword(); return md5($plain . $authPassword['salt']) == $authPassword['password']; } }
3. 將User Providers換成我們自己的GfzxEloquentUserProvider
修改 app/Providers/AuthServiceProvider.php
<?php namespace App\Providers; use App\Foundation\Auth\GfzxEloquentUserProvider; use Auth; use Illuminate\Support\Facades\Gate; use Illuminate\Foundation\Support\Providers\AuthServiceProvider as ServiceProvider; class AuthServiceProvider extends ServiceProvider { . . . /** * Register any authentication / authorization services. * * @return void */ public function boot() { $this->registerPolicies(); Auth::provider('gfzx-eloquent', function ($app, $config) { return new GfzxEloquentUserProvider($this->app['hash'], $config['model']); }); } }
4. 修改 config/auth.php
'providers' => [ 'users' => [ 'driver' => 'gfzx-eloquent', 'model' => App\Models\User::class, ], ],
這是就可以用過salt+passwrod的方式密碼認證了
文章參考
到此這篇關于laravel修改用戶模塊的密碼驗證實現(xiàn)的文章就介紹到這了,更多相關laravel修改用戶模塊的密碼驗證內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關文章希望大家以后多多支持腳本之家!
相關文章
php下獲取Discuz論壇登錄用戶名、用戶組、用戶ID等信息的實現(xiàn)代碼
前面有一篇文章講過自己從cookie和discuz數(shù)據(jù)庫中取用戶名、用戶組、用戶ID等信息,但那個并不一定準確,因為discuz登錄時會使用COOKIE中的auth值來動態(tài)登錄,而cookie信息是滯后的,所以獲取到的信息并不完全準確。2010-12-12微信網(wǎng)頁授權(OAuth2.0) PHP 源碼簡單實現(xiàn)
這篇文章主要為大家詳細介紹了微信網(wǎng)頁授權(OAuth2.0) PHP 源碼簡單實現(xiàn),具有一定的參考價值,感興趣的小伙伴們可以參考一下2016-08-08windows7配置Nginx+php+mysql的詳細教程
這篇文章主要介紹了windows7配置Nginx+php+mysql的詳細教程 的相關資料,需要的朋友可以參考下2016-09-09用Laravel Sms實現(xiàn)laravel短信驗證碼的發(fā)送的實現(xiàn)
這篇文章主要介紹了用Laravel Sms實現(xiàn)laravel短信驗證碼的發(fā)送的實現(xiàn),小編覺得挺不錯的,現(xiàn)在分享給大家,也給大家做個參考。一起跟隨小編過來看看吧2018-11-11ThinkPHP V2.2說明文檔沒有說明的那些事實例小結(jié)
這篇文章主要介紹了ThinkPHP V2.2說明文檔沒有說明的那些事,實例分析了ThinkPHP中常用的技巧,需要的朋友可以參考下2015-07-07PHP設計模式(八)裝飾器模式Decorator實例詳解【結(jié)構(gòu)型】
這篇文章主要介紹了PHP設計模式:裝飾器模式Decorator,結(jié)合實例形式分析了PHP裝飾器模式Decorator相關概念、功能、原理、用法及操作注意事項,需要的朋友可以參考下2020-05-05PHP中為什么使用file_get_contents("php://input")接收微信通知
微信用戶和公眾號產(chǎn)生交互的過程中,用戶的某些操作會使得微信服務器事件推送,通知到開發(fā)者中心設置的服務器地址(回調(diào)url),開發(fā)者可以獲取到該信息。PHP中為什么使用file_get_contents("php://input")來接收呢?為什么有些場景php://input接收不到?2023-07-07配置Apache2.2+PHP5+CakePHP1.2+MySQL5運行環(huán)境
因為最近要用PHP做個小東西,新學了PHP。結(jié)果學PHP只用了2個小時,配置服務器卻用了兩天,郁悶得想罵人。為了避免以后忘掉,寫個博客留底。2009-04-04