Fix mqtt_demo_mutual_auth username parameters for client authentication #1893
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
ActoryOu
reviewed
Oct 20, 2023
ActoryOu
approved these changes
Oct 20, 2023
chinglee-iot
changed the title
aggarg
approved these changes
Oct 23, 2023
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.
Support parameters in CLIENT_USERNAME
Description
Before this PR, CLIENT_USERNAME can't be appended with extra parameters. These parameters are used in client authentication to specify token, signature and authorizer.
Test
Specify the authorizer in CLIENT_USERNAME should be able to connect to AWS IoT core.
For example,
Issue
#1885
By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.