Add insecure TLS option to mqtt test#710
Open
schmitz-chris wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Adds
--insecuretomqtt testso users can deliberately run TLS broker tests while ignoring certificate/trust validation failures.Details
--insecureonly onTestBrokerCommandTlsOptionsthrough a programmatic toggle, so publish/subscribe/shell TLS options are not broadenedTrustManagerFactoryplus hostname verifier only when insecure mode is explicitly enabled--securebehavior on the default trust and hostname validation pathValidation
./gradlew compileJava./gradlew test --tests '*TestBrokerCommand*' --tests '*TlsOptions*'./gradlew testPi Loop reviewer: Claude Sonnet 4.6 promoted the iteration with zero findings.