Skip to content

Commit

Permalink
fix hashing name
Browse files Browse the repository at this point in the history
  • Loading branch information
@taylorotwell
taylorotwell committed May 5, 2020
1 parent 1176eb5 commit a9043df
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion UPGRADE.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Passport now has support for multiple guard user providers. Because of this chan

PR: https://github.com/laravel/passport/pull/1145

Client secrets may now be stored using a SHA-256 hash. However, before enabling this functionality, please consider the following. First, there is no way to reverse the hashing process once you have migrated your existing tokens. Secondly, when hashing client secrets, you will only have one opportunity to display the plain-text value to the user before it is hashed and stored in the database.
Client secrets may now be stored using a Bcrypt hash. However, before enabling this functionality, please consider the following. First, there is no way to reverse the hashing process once you have migrated your existing tokens. Secondly, when hashing client secrets, you will only have one opportunity to display the plain-text value to the user before it is hashed and stored in the database.

You may enable client secret hashing by calling the `Passport::hashClientSecrets()` method within the `boot` method of your `AppServiceProvider`. For convenience, we've included a new Artisan command which you can run to hash all existing client secrets:

Expand Down

0 comments on commit a9043df

Please sign in to comment.