Disable TLS-E #393
Merged
Disable TLS-E #393
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
Set TLS-E to disabled, since it's being enabled by default for greenfield deployments. Settings should not be changed during adoption, and the currently tested scenario doesn't support TLS-E. This also adds a barbican section that's present in the docs but missing in the tests.
jistr
approved these changes
Apr 2, 2024
fao89
approved these changes
Apr 2, 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.
Set TLS-E to disabled, since it's being enabled by default
for greenfield deployments. Settings should not be changed
during adoption, and the currently tested scenario doesn't
support TLS-E.
This also adds a barbican section that's present in the docs
but missing in the tests.