New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openIdConnectUrl is required with apiKey security schema type #50
Comments
slinkydeveloper
added a commit
to slinkydeveloper/KaiZen-OpenApi-Parser
that referenced
this issue
Jul 20, 2017
Closed
andylowry
added a commit
that referenced
this issue
Sep 15, 2017
This PR prevents the NPE situation in the reported example, but it does not properly handle `operationRef` values, and creates a validation warning stating this. The problem is that, in all of OpenAPI 3.0, this is the *one* place where a reference string can appear outside a reference object! And reference handling resolves ref strings in ref objects but does not have a way of resolving other ref strings. So this is a stop-gap until the necessary functionality can be added to support this properly.
andylowry
added a commit
that referenced
this issue
Sep 18, 2017
File now reflects renaming of `href` to `operationRef` in `Link` objects.
andylowry
added a commit
that referenced
this issue
Sep 18, 2017
[#50] Fix test yaml for BigParseTest
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why "
openIdConnectUrl
is required" is thrown when security schema type isapiKey
? It seems useless with an api key security. It throw the same error withbasic
security type. For example:The text was updated successfully, but these errors were encountered: