-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Has the Authorize button been implemented for OAS3.0? It does not display. #3665
Comments
Authorization is not yet supported in OAS3. |
Hi @webron, ¿Do you have some time estimation for having this functionality working in OAS3? Thanks in advance! Diego. |
@gartediego Expanding OAS3 support is our main focus right now. The functionality is expected to be available within the next few weeks. Whether it's 2 weeks, 6 or 10, I can't tell you. |
Thanks @webron! |
@webron Do you have any updates related this functionality? Thanks. |
The authorization is the current feature we're working on. Not sure if it'll make it to this week's release but it should be available by next week's. |
Closing - the original question has been answered, and we have other tickets for tracking the OAS3 Authorization feature. Thanks everyone! |
@shockey: What's the number of the issue I should be keeping an eye on to know whether that feature's been fixed / added? |
I'm sorry if this is a duplicate...I could not find a related issue.
Should I be able to see the Authorize button when using OAS3.0?
I copied this petstore swagger 2.0 json file, converted it to OAS3.0 using this, pointed my swagger-ui at it, but cannot see the Authorize button.
The authorize button is visible for the Swagger 2.0 json file that I converted. I figure something went wrong with the conversion from 2.0 to 3.0...or it hasn't been implemented yet.
Demonstration API definition
Expected Behavior
See the Authorize button
Current Behavior
Authorize button is not displayed
Possible Solution
Wait or help with the outstanding work...I assume it hasn't been implemented yet for OAS3.0.
Context
I am trying to define and display a response where the object's type can vary using the oneOf feature.
My understanding is that oneOf only works with OAS3.0.
The text was updated successfully, but these errors were encountered: