Tenant password reset token is being stored on landlord password_reset_tokens table. #482
Unanswered
pratikkuikel
asked this question in
Q&A
Replies: 2 comments
-
Hi @herecomeslucky0145, try with: 'passwords' => [
'landlords' => [
'provider' => 'landlords',
'connection' => 'your-landlord-connection',
'table' => 'password_reset_tokens',
'expire' => 60,
'throttle' => 60,
],
'tenants' => [
'provider' => 'tenants',
'connection' => 'your-tenant-connection',
'table' => 'password_reset_tokens',
'expire' => 60,
'throttle' => 60,
],
], |
Beta Was this translation helpful? Give feedback.
0 replies
-
If you are using Fortify, add this to your boot method of the FortifyServiceProvider class: // This will make the password reset record in the password_reset_tokens table of the landlord or tenant-specific database.
Tenant::checkCurrent()
? Config::set('auth.passwords.users.connection', 'tenant')
: Config::set('auth.passwords.users.connection', 'landlord'); |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am using filamentphp v3 with AdminPanel and TenantPanel, At the end of configuring and testing password resets I noticed that : for the password reset tokens the
password reset
requested from tenant panel is being stored to landlord database, while the reset works just fine. I wonder what is causing this behavior ! , Everything works fine despite the tenant password resets being stored on landlord's table.The password reset mail just works with the tenant subdomain and the password reset is successfull but I find this behavior weird.
I need some guidance.
I am using different password brokers for landlord and tenant :
landlord password resets works too. Everything is working as expected.
Beta Was this translation helpful? Give feedback.
All reactions