Optional refresh token in implicit grant #108
Merged
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.
Solution proposal for issues: #98.
This commit includes additional logic to make the generation of refresh tokens optional in implicit grant flows so that this package becomes strictly compliant with the OAuth 2.0 specification in section 4.2. To see further information, please refer to issue #98.
To not break backward compatibility, this new option has been included as an new optional setting flag,
ISSUE_REFRESH_TOKEN_IMPLICIT_GRANT
, that when set toFalse
, it deactivates the refresh token generation in implicit flows.