Get a password reset token

@josh18 That seems fine to me if you want to provide additional static access to it. Like all bindings you could alway use it directly if needed.

app('auth.password.tokens')->create($user);

If you're intrigued as to where the binding and setup of the DatabaseTokenRepository takes place. Illuminate\Auth\Passwords\PasswordResetServiceProvider

If you use the out the box PasswordController with ResetsPasswords trait, what the PasswordBroker does is actually type hint the interface TokenRepositoryInterface to new this up. As you can see in Illuminate\Foundation\Application it's an alias for the same binding.

public function registerCoreContainerAliases()
{
...
'auth.password.tokens' => 'Illuminate\Auth\Passwords\TokenRepositoryInterface',

I'm not anti Facade but I would use the alias personally.

use Illuminate\Auth\Passwords\TokenRepositoryInterface;

Route::get('/reset', function (TokenRepositoryInterface $tokens) {

    $user = ...
    $tokens->create($user);
});

Ugh.... app('auth.password.tokens')->create($user); is exactly what I need. Thanks for your help and sorry for the stupid question.

I'm sure it's somewhere obvious but you can you point me to the right direction in the docs (5.1) where it talks about this? I've browsed the docs quite a lot and the only similar things I have seen are app()->environment(); (installation page) and the list on the facade page (hence why I thought they were only accessible via facades).

For future reference if I were to make a facade how would I go about implementing it? I tried moving my new facade from Illuminate/Support/Facades to app/Facades and changing the alias in app.php but I couldn't seem to get it working for some reason.

@josh18 http://laravel.com/docs/5.1/container#resolving

@josh18 The app() function returns the Container instance or resolves if passed a string of what to make. The Container implements ArrayAccess too so you can also use it like app()['auth.password.tokens'].

For future reference if I were to make a facade how would I go about implementing it?

Re the Facade the 5.0 doc is actually better at explaining it with step by step.

• 1. create the class
• 2. create the binding
• 3. create the Facade which references that binding.

http://laravel.com/docs/5.0/facades#creating-facades

For Laravel 5.3 it's now:

app('auth.password.broker')->createToken($user);

Sorry to dig up this old thread, in a situation where I need to manually send a password reset token to users.

If I generate the token using app('auth.password.broker')->createToken($user);

And insert it into an email, I receive the email just as you'd expect. But when trying to reset the password, I get an Invalid Token. I have confirmed that the token is being inserted into the database.

If I attempt to reset my password the traditional way /password/reset, everything works great.

Any ideas? On Laravel 5.5

Odd..I have a method on my user class to generate the token, I was calling that from my mail view. If I move that token generation to the Mailable item and inject the token into the view it works fine...Guessing somewhere the generateToken method was being called twice. Overriding the initial token value..

Hi!

I know this post is kind of old but for Laravel 5.5 and I think more recent versions We can achieve that with this:

$token = app(Illuminate\Auth\Passwords\PasswordBroker::class)->createToken($user);

Greetings!

just adding to this thread for users of L6* who like Facades *I've no idea from when this became valid..

include the facade at the top of your controller use Illuminate\Support\Facades\Password;

call it in a function... $token = Password::broker()->createToken($user);