feat: added token prefix option #652
Closed
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
|
May I suggest a slight modification, rather than defining the prefix, make both the token cookie and refresh cookie names configurable. Doing so would then solve for #650 due to |
|
that's a perspective I hadn't considered. Thank you for sharing it! |
|
I have created the following pull request: #654. I will close this PR now. |
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.
We will make it possible to change the prefix of the token stored in the Cookie upon refresh when using the local type or refresh type.
The reason this is necessary: When multiple environments are launched on localhost, conflicts occur in the token storage locations.
Checklist:
#)