Add description of how to update custom claims on refresh to README #60
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.
Adds a description of how to update custom claims on token refresh requests. This expands the section of the README called "Customizing token claims" and the added description's structure mirrors that of the existing "Customizing token claims" section.
This is helpful to include because it is not uncommon for token data to become outdated quicker than refresh tokens expire on average. Issue 33 was a question about this sort of behavior and this added description borrows from the response to issue 33 by davesque. Similarly, issue 59 (about revoking refresh tokens if the user's password is changed) would benefit from this description.