microsoft / microsoft/typespec
Add support for converting auth schemes in openapi to tsp converter
- Dominant language
- Java
- Stars
- 5.9k
- Forks
- 394
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 104
Description
### Describe the bug
I have a private OpenAPI 3.0 JSON spec that has valid `"securitySchemes"` and `"security"` features with bearer and oauth2 sub-elements (I've validated these by making swagger config changes in my code), but when I use the playground to import this spec into a tsp I see no mention of `@useAuth` in the output. Is there something I might be missing? Or is this a known gap of the playground?
### Reproduction
A minimal reproduction JSON with a small test API is attached. Notice that if you import this into the playground the tsp output will have no mention of `@useAuth`.
[test_api.json](https://github.com/user-attachments/files/16257853/test_api.json)
### Checklist
- [X] Follow our [Code of Conduct](https://github.com/microsoft/typespec/blob/main/CODE_OF_CONDUCT.md)
- [X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/Microsoft/typespec/discussions).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
Contributor guide
Assessment
This issue has not been assessed yet.