Change default for V1_3 compatibility to false #435
Merged
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
There should be no need to maintain compatibility with insecure tokens from Fabric v1.3. The default is now to require secure tokens. Compatibility with the old secure tokens can still be enabled by settings the FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3 environment variable to "true". Signed-off-by: Mark S. Lewis <[email protected]>
denyeart
approved these changes
Oct 7, 2024
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.
There should be no need to maintain compatibility with insecure tokens from Fabric v1.3. The default is now to require secure tokens. Compatibility with the old insecure tokens can still be enabled by settings the FABRIC_CA_SERVER_COMPATIBILITY_MODE_V1_3 environment variable to "true".
Closes #434