-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
security and securitySchemes do not recognize apiKey or httpApiKey types #914
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
@nicolasmohamed some properties are missing in your security definition: For apikey for instance:
You can check the doc |
Hi @Amzani , when I tried to reproduce the issue, the problem seems to be only in httpApiKey as apiKey as a value does not show any error. Has the issue been partially fixed or am I missing something? |
It's not a bug @helios2003 |
Describe the bug
If type field equals to apiKey, AsyncAPI Studio shows the following error:
"type" property must be equal to one of the allowed values: "userPassword", "X509", "http", "httpApiKey", "oauth2", "openIdConnect". Did you mean "httpApiKey"?
If type field equals to httpApiKey, AsyncAPI Studio shows the following error:
"type" property must be equal to one of the allowed values: "userPassword", "apiKey", "http", "oauth2", "openIdConnect". Did you mean "apiKey"?
How to Reproduce
same for:
Expected behavior
AsyncAPI Studio should render correctly as apiKey and httpApiKey are both valid types.
Thanks!!
The text was updated successfully, but these errors were encountered: