Release/v0.4.1 #93
Merged
Release/v0.4.1 #93
Conversation
This file contains 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
Fix Auth Expiration time filter and add it to documentation
Update php-jwt to latest version
…-set #87 - Force Auth Secret to be set, else throw Exception
- Update version number for release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release Notes
Breaking changes
graphql_jwt_auth_expirehas been fixed to take the filtered value and add it to the issue date. So, you can use the filter, return a value of600and that will add 600 seconds to the issue date, and your token will expire 10 minutes after issue. If you were using this filter already, and were doing this math yourself, you should update to just return the number of seconds after issue you would like the token to expire.Bugfixes
graphql_jwt_auth_expirefilter. Thanks @henrikwirth!New Features
GRAPHQL_JWT_AUTH_SECRET_KEY