Send CryptKey instance to oauth2 with new permission check disabled #3
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.
When running in some development environments, eg Vagrant on Windows (or most other methods you might use to develop in windows, eg docker or a local PHP install) it's impossible to make the oauth-private.key file match the exact permissions that thephpleague/oauth2-server now checks for, and this means everything will fail with an exception
Passport fixed this in this PR laravel/passport#454 and this code implements a similar solution in benbjurstrom/passport-custom-jwt-claims