Ich habe mehrere Authentifizierung in Laravel 5.2 getan, alles funktioniert gut. Ich bin in der Lage, Admin zu authentifizieren, umleiten zu Dashboard und Abmelden erfolgreich. Aber das Problem ist, dass, wenn Benutzer nicht authentifiziert wird und ich die Route des Dashboards in die URL einfüge, das Dashboard öffnet, selbst wenn der Admin nicht authentifiziert ist.Routen in Laravel 5.2 werden nicht automatisch zur Anmeldung weitergeleitet, wenn nicht authentifiziert
My Admin Modell
<?php
namespace App\Models;
use Illuminate\Foundation\Auth\User as Authenticatable;
class System_admin extends Authenticatable
{
protected $guard="admins";
protected $table="system_admin";
protected $primaryKey="admin_id";
protected $fillable = [
'admin_name', 'admin_email', 'admin_password','city_id','admin_address','admin_mobile','admin_status'
];
public function getAuthPassword() {
return $this->admin_password;
}
}
Meine config/Auth.php
<?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' => 'token',
'provider' => 'users',
],
//for admin
'admins' => [
'driver' => 'session',
'provider' => 'admins',
],
],
/*
|--------------------------------------------------------------------------
| 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\Models\User::class,
],
//for admin
'admins' => [
'driver' => 'eloquent',
'model' => App\Models\System_admin::class,
],
// 'users' => [
// 'driver' => 'database',
// 'table' => 'users',
// ],
],
/*
|--------------------------------------------------------------------------
| Resetting Passwords
|--------------------------------------------------------------------------
|
| Here you may set the options for resetting passwords including the view
| that is your password reset e-mail. You may also set the name of the
| table that maintains all of the reset tokens for your application.
|
| 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',
'email' => 'auth.emails.password',
'table' => 'password_resets',
'expire' => 60,
],
'admins' => [
'provider' => 'admins',
'email' => 'auth.emails.password',
'table' => 'password_resets',
'expire' => 60,
],
],
];
Meine Middleware AdminAuth.php
<?php
namespace App\Http\Middleware;
use Closure;
use Illuminate\Support\Facades\Auth;
class AdminAuth
{
/**
* Handle an incoming request.
*
* @param \Illuminate\Http\Request $request
* @param \Closure $next
* @param string|null $guard
* @return mixed
*/
public function handle($request, Closure $next, $guard = 'admins')
{
if (Auth::guard($guard)->guest()) {
if ($request->ajax()) {
return response('Unauthorized.', 401);
} else {
return redirect()->guest('/admin');
}
}
return $next($request);
}
}
app/kernel.php
<?php
namespace App\Http;
use Illuminate\Foundation\Http\Kernel as HttpKernel;
class Kernel extends HttpKernel
{
/**
* The application's global HTTP middleware stack.
*
* These middleware are run during every request to your application.
*
* @var array
*/
protected $middleware = [
\Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode::class,
];
/**
* The application's route middleware groups.
*
* @var array
*/
protected $middlewareGroups = [
'web' => [
\App\Http\Middleware\EncryptCookies::class,
\Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
\Illuminate\Session\Middleware\StartSession::class,
\Illuminate\View\Middleware\ShareErrorsFromSession::class,
\App\Http\Middleware\VerifyCsrfToken::class,
],
'admins' => [
\App\Http\Middleware\EncryptCookies::class,
\Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse::class,
\Illuminate\Session\Middleware\StartSession::class,
\Illuminate\View\Middleware\ShareErrorsFromSession::class,
\App\Http\Middleware\VerifyCsrfToken::class,
],
'api' => [
'throttle:60,1',
],
];
/**
* The application's route middleware.
*
* These middleware may be assigned to groups or used individually.
*
* @var array
*/
protected $routeMiddleware = [
'admins' => \App\Http\Middleware\AdminAuth::class,
'auth' => \App\Http\Middleware\Authenticate::class,
'auth.basic' => \Illuminate\Auth\Middleware\AuthenticateWithBasicAuth::class,
'guest' => \App\Http\Middleware\RedirectIfAuthenticated::class,
'throttle' => \Illuminate\Routing\Middleware\ThrottleRequests::class,
];
}
LoginController.php
<?php
namespace App\Http\Controllers\admin;
use Illuminate\Http\Request;
use App\Http\Requests;
use App\Http\Controllers\Controller;
use \Auth;
use Session;
class LoginController extends Controller
{
public function viewlogin()
{
return view('admin.login');
}
public function checklogin(Request $request)
{
$credentials=array('admin_email' => $request->input('email'),'password' => $request->input('password'));
if(Auth::guard('admins')->attempt($credentials))
return redirect()->intended('/admin/dashboard');
else
return redirect('/admin')->with('error','Invalid Username or Password');
}
public function logout()
{
Auth::guard('admins')->logout();
return redirect()->intended('/admin');
}
}
Routen
Route::group(['middleware' => ['admins']], function()
{
Route::get('/admin','Admin\[email protected]');
Route::post('/admin/login','Admin\[email protected]');
Route::get('/admin/dashboard','Admin\[email protected]');
Route::get('/admin/logout','Admin\[email protected]');
Route::resource('/admin/movies','Admin\MovieController');
Route::resource('/admin/states','Admin\StateController');
Route::resource('/admin/cities','Admin\CityController');
Route::resource('/admin/tax','Admin\TaxController');
Route::resource('/admin/smsgateway','Admin\SmsgatewayController');
Route::resource('/admin/smtpgateway','Admin\SmtpgatewayController');
Route::resource('/admin/paymentgateway','Admin\PaymentgatewayController');
});
Route::group(['middleware' => ['web']], function() {
});
Wenn ich angemeldet bin in und ich öffne Armaturenbrett dann kann ich die Anmeldeinformationen von protokollierten Admin sehen.
Aber wenn ich mich wieder auslogge und wieder Armaturenbrett besuchen sollte es umleiten um sich einzuloggen, aber es ist nicht Umleiten Seite einzuloggen.
Bitte helfen Sie mir da keiner von Fragen auf Stackoverflow, die Antwort hat bekam die ich suche.
Wenn ich diesen Code hinzufügen Route :: group (['Middleware' => ['Admins', 'Auth']], Funktion() {..} dann wird es zu Middleware/Authenticate.php gehen und ist Weiterleiten an etwas anderes, das ich nicht möchte – dollar
so erstellt Ihre eigene Authentifizierung und Middleware, um Ihre Anforderungen zu erfüllen, wie die integrierten sind anpassbar und editierbar? –
Ja simon, wie ich 4 Arten von Benutzern zu ie Wallet User, Admin, Staff und Service Benutzer, ich dachte, es wäre besser, eigene Authentifizierung und Middleware zu erstellen ..Aber ich stecke hier fest – dollar