Replace reset password with fortify #207
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pushpak1300
force-pushed
the
replace_email_verification_with_fortify
branch
2 times, most recently
from
688a72a to
4c879d7
Compare
pushpak1300
force-pushed
the
replace_password_reset_with_fortify
branch
from
d3a8e7c to
034974c
Compare
This was referenced Oct 12, 2025
…assword_reset_with_fortify # Conflicts: # app/Providers/FortifyServiceProvider.php
pushpak1300
force-pushed
the
replace_password_reset_with_fortify
branch
from
992c30b to
307996e
Compare
…assword_reset_with_fortify
pushpak1300
force-pushed
the
replace_password_reset_with_fortify
branch
from
a9972f0 to
6d7577c
Compare
pushpak1300
commented
Oct 13, 2025
Comment on lines
+16
to
+20
| Route::get('settings/password', [PasswordController::class, 'edit'])->name('user-password.edit'); | ||
|
|
||
| Route::put('settings/password', [PasswordController::class, 'update']) | ||
| ->middleware('throttle:6,1') | ||
| ->name('password.update'); | ||
| ->name('user-password.update'); |
There was a problem hiding this comment.
During this integration, we identified a route name conflict between our existing setting password update route and Fortify’s built-in password reset route. Previously, it was defined as: password.update & password.edit which conflicted with Fortify’s internal route. To resolve this, we updated it to: user-password.update & user-password.edit same as per fortify conventions
joetannenbaum
approved these changes
Oct 13, 2025
This was referenced Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Part 3: Password Reset)
This MR replaces the existing password reset logic with Fortify’s built-in implementation.
All routes, actions, and validation logic are now handled via Fortify.
The existing views remain unchanged, while the backend logic is fully transitioned to Fortify.
Feature toggles in
fortify.phpto behave as expected, allowing password reset functionality to be easily enabled or disabled which reflect in the UI.'password.update'&'password.edit'which conflicted with Fortify’s internal route. To resolve this, we updated it to:'user-password.update'&user-password.edit'Related Merge Requests