Optional authFields for JWT payload. #42
Open
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.
A project that I'm currently working on for school uses this library (so thank you for that).
However, we needed more data in the JWT payload (specifically a role). So I added some code to account for that.
Putting it simply, if you want a field to be sent in the JWT payload, add it to the
authFields
when creating the user, like so:The
accessToken
returned will contain the email, sub (id), and any other fields that are in the authFields array.And as a bonus, its retroactive. So any existing users in the db.json that you would like the JWT payload to return more fields on, just add the authFields array to it, and it'll work.