Instantiate TFA #262
Draft
Instantiate TFA #262
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
…l default value could be problematic.
…WARNs that null default null values could be problematic.
|
At the moment, @EnigmaCurry, this only works if you leave COOKIE_NAME to the default value of "_forward_auth" (and you have to make sure that TRAEFIK_FORWARD_AUTH_SECRET is the same value as it is for the other TFA instances since they're all using the same cookie name - otherwise apps using one TFA instance will authenticate and others will fail). If you set COOKIE_NAME to something unique, like "_forward_auth_context_instance", you get infinite redirects between |
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.
Adding instances to TFA, mainly so we can define COOKIE_NAME so it differs between TFA on different servers.
This will fix #261