Support multiple specs in asyncapi binding#982
Merged
Conversation
jfallows
requested changes
Apr 26, 2024
Comment on lines
+142
to
+146
| //TODO: change when jwt support added for mqtt in asyncapi | ||
| //if ("jwt".equals(guardType)) | ||
| //{ | ||
| // result.put(securitySchemeName, guardType); | ||
| //} |
Contributor
There was a problem hiding this comment.
Is this TODO still relevant?
Contributor
Author
There was a problem hiding this comment.
I think yes. As asyncapi doesn't have JWT support added for MQTT yet and we use this to determine if we need to add the mqtt authorization options for the server. If we filter for "jwt" we'll never add those options.
jfallows
approved these changes
Apr 30, 2024
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
2 participants
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.
No description provided.