-3
I have a project in laveral 5.3 that I am building an administration.
I already have the whole database structure created. I now want to login with fields username
and password
. You won’t have a public record, just log in.
I’ve already created a system, but it’s not working, because
indicates to me that the table users
does not exist. I just want to use my own tables and do not know how, and I want it to be a secure login with validations.
If you can help me.
Routes
Route::get('admin/login', 'admin\LoginController@showLogin'); // Mostrar login
Route::post('admin/login', 'admin\LoginController@postLogin'); // Verificar datos
Route::get('admin/logout', 'admin\LoginController@logOut'); // Finalizar sesión
Route::group(['before' => 'auth'], function()
{
Route::get('admin', function (){
});
});
Controller Login
namespace App\Http\Controllers\admin;
use Illuminate\Http\Request;
use App\Http\Controllers\Controller;
use DB;
use Auth;
use Illuminate\Support\Facades\Input;
class LoginController extends Controller{
public function showLogin (){
if (Auth::check()){
return Redirect::to('/admin');
}
return view('admin/login');
}
public function postLogin(){
$data = [
'username' => Input::get('username'),
'password' => Input::get('password')
];
if (Auth::attempt($data, Input::get('remember')))
{
return Redirect::intended('admin');
}
return Redirect::back()->with('error_message', 'Invalid data')->withInput();
}
public function logOut(){
Auth::logout();
return Redirect::to('admin/login')->with('error_message', 'Logged out correctly');
}
}
Config.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',
],
],
/*
|--------------------------------------------------------------------------
| 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,
],
],
];
What is Laveral ?
– Diego Souza
Although the version is different, the process is the same.
– Diego Souza
I had to see but this version is not the same as they say there to do
– César Sousa
Laravel’s own authentication system has its validations. If you change the table, it won’t change the security. If you want additional validations, you can use the Laravel Validator for this purpose. I think the question has gotten a little wide.
– Wallace Maxters
You can add fields, make relationships with the same table, exchange it for another can mean you need to write code and know how the process works, it’s not easy, but, it’s possible, I just believe it’s unnecessary. Do with the current table even, and with the same class it saves time, updates are always happening etc ...
– novic
@Diegosouza I believe that it is not duplicated, because it changes a lot of the
Laravel 5.1
to the5.3
– Felipe Paetzold