In the exported OpenAPI Spec, the (OAuth2) is not added to each endpoint as securitySchemes

Bug Report
1

In the⁠ exported OpenAPI Spec, the (OAuth2) is not added to each endpoint as securitySchemes:
https://swagger.io/docs/specification/v3_0/authentication/oauth2/

image.png
image.png704×925 50.4 KB

2

Thanks for the feedback, we will think about how to optimize it.

3

So this is a known bug?

4

because this is a block for us; we need to have a fully corrected OpanAPI spc file as per the standards with considering the OAuth2.

5

Currently, exporting OAuth2.0 as security scheme is not supported, but we are developing it and it is expected to be released this week.

6

In addition, we are developing security scheme features that are fully compatible with OAS. You can create security schemes and then reference them within the endpoints. This new feature will be released next month.

7

hi Evans is there any update here please?

8

Hi jam_zaw ,
Thank you for your query! We’re excited to share that the feature is expected to be released by next week.

We appreciate your patience and support as we work on bringing this to you. If you have any other questions or need assistance, feel free to reach out.

Thank you! :blush:

9

Thanks!

10

jam_zaw Now when you export the project as an OAS file, the OAuth 2.0 configured for the endpoint will be converted into a security scheme.

11

Evans highly appreciated. we will give it a test asap