-
-
Notifications
You must be signed in to change notification settings - Fork 56
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 scheme object is not working as per docs #444
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. |
Adding context: I confirm this is a bug with the following test: https://www.jsonschemavalidator.net/s/58zmJBLh |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
So the validation is correct. |
Describe the bug
I get
Property name is not allowed.yaml-schema: AsyncAPI 3.0.0 schema.(0)
when usingname
parameter inSecurity Scheme Object
in v3 spec.How to Reproduce
Link for document in Studio.
Expected behavior
As per docs we should be able to use the
name
parameter in the AsyncAPI document underSecurity Scheme Object
.The text was updated successfully, but these errors were encountered: