Allow the name of the account id field to be configured via .env #4
Conversation
This file contains hidden or 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
gboyegadada
approved these changes
Jun 20, 2017
Owner
gboyegadada
left a comment
gboyegadada
left a comment
There was a problem hiding this comment.
Hi Michael, thanks for this!
Contributor
Author
|
Thank you for this project! I definitely plan to keep using it, and am happy to keep adding the occasional little feature like this as I come across use cases for them :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 user provider that looks up accounts via a field other than
idcan now be used, by supplying a custom value for the new keyJWT_ID_FIELDin the .env file. This field is always included in the resulting token and defaults to"id"when not specified.