Add COUPLE_SESSION_WITH_COOKIE_NAME env var #1881
Open
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
This means the user's session will be reset if the value of the coupled cookie name changes. Useful if the app is deployed on a subpath of another site, and you want to reset the session when the auth for the user changes
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.
This means the user's session will be reset if the value of the coupled cookie name changes. Eg if the
tokencookie changes, the user's session will be reset (ifCOUPLE_SESSION_WITH_COOKIE_NAME=token)Useful if the app is deployed on a subpath of another site, and you want to reset the session when the auth for the user changes
Alternative to #1877 - with a broader oauth support (inference request made using oauth token, supprt for oauth refresh token, support for auto-redirecting to oauth if user is not logged in, ...) we can keep using oauth, while handling when the user changes accounts on the main site