You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to Passport v9, enabling hashed client secrets (Passport::hashClientSecrets()), and running the command to hash the secrets in the database, we are unable to create Personal Access Tokens.
When using the included Vue component, we receive a 500 (Client authentication failed) when trying to create a new Personal Access Token.
Strangely, even after hashing the client secrets in the database, removing the Passport:hashClientSecrets() method from the AppServiceProvider fixes the issue and allows Personal Access Tokens to be created.
The text was updated successfully, but these errors were encountered:
Hey @aaronhuisinga. We've released v9.1.0 which fixes this.
Unfortunately we weren't able to fix this without introducing a new breaking change. If you already hashed the secret of your personal access client in production you'll have to generate a new one and set its client id and secret in your .env file. Here's steps on how to do that: https://github.com/laravel/passport/blob/9.x/UPGRADE.md#personal-access-clients
We're very sorry about this. Unfortunately we didn't caught this in the original pull request that was sent in.
Description:
After upgrading to Passport v9, enabling hashed client secrets (Passport::hashClientSecrets()), and running the command to hash the secrets in the database, we are unable to create Personal Access Tokens.
When using the included Vue component, we receive a 500 (Client authentication failed) when trying to create a new Personal Access Token.
Strangely, even after hashing the client secrets in the database, removing the Passport:hashClientSecrets() method from the AppServiceProvider fixes the issue and allows Personal Access Tokens to be created.
The text was updated successfully, but these errors were encountered: