Fixed problem with custom security schemas #166
Closed
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
|
@psotres did you sign our CLA? |
|
@psotres LGTM. Have you signed our CLA? |
|
@psotres: You can find our CLA at https://api-notebook.anypoint.mulesoft.com/notebooks#bc1cf75a0284268407e4. |
|
@psotres any updates? seems you would also need to merge the current master back to your branch. |
|
Sorry, I just signed the CLA. However don't merge this PR, I will send another one with some extra security scheme related bugs fixed. |
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.
According to the spec, any "x-{}" schema should work. This should fix #145 and #149.
Anyway the "Unknown authentication strategy" error that is thrown at "common/client/auth_strategies.js" is still unhandled and that error is not shown anywhere.