-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Laravel 10.10 - Cast password "hashed" #479
Comments
Verify reported issue: laravel/fortify#479 Signed-off-by: Mior Muhammad Zaki <[email protected]>
Hey there, thanks for reporting this issue. We'll need more info and/or code to debug this further. From our own tests, this is not possible laravel/framework#47904 Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here? Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.
Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue. Thanks! |
Why do think the password is being hashed twice? when casting to |
the line you shown check if value hasn't been hashed and in that case should be hashed.. |
* [10.x] Test Improvements for `hashed` password Verify reported issue: laravel/fortify#479 Signed-off-by: Mior Muhammad Zaki <[email protected]> * wip Signed-off-by: Mior Muhammad Zaki <[email protected]> --------- Signed-off-by: Mior Muhammad Zaki <[email protected]>
Hello,
From the Laravel 10.10 version, we can cast a password directly in the model with "hashed" so we don't need anymore to hashed this password in the code.
Do you think that we will change our code to take this feature in consideration ?
Now, each time when I instal or upgrade Fortify, I need to change the code again to avoid a dubble hashing of the password :-)
Thanks
The text was updated successfully, but these errors were encountered: