OpenAPITools / OpenAPITools/openapi-generator
[BUG] kotlin-spring oauth does not work
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue?
- Have you validated the input using an OpenAPI validator (example)?
- What's the version of OpenAPI Generator used? 4.3.0
- Have you search for related issues/PRs?
- What's the actual output vs expected output?
- [Optional] Bounty to sponsor the fix (example)
Description
I tried running the petstore.yaml example (that include oauth implicit security), but no oauth code is generated. I tried via npm cli and docker cli.
openapi-generator version
via docker I also tried v4.0.0 and v3.3.4 with no success
OpenAPI declaration file content or url
petstore.yaml 2.0 or petstore.yaml 3.0
Command line used for generation
docker run --rm -v ${PWD}:/local openapitools/openapi-generator-cli generate
-i https://raw.githubusercontent.com/openapitools/openapi-generator/master/modules/openapi-generator/src/test/resources/2_0/petstore.yaml
-g kotlin-spring
-o /local/web
Steps to reproduce
Related issues/PRs
Suggest a fix
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the provided Docker generation command with the linked OpenAPI 2.0 and 3.0 petstore.yaml inputs and the kotlin-spring generator. Inspect the kotlin-spring OAuth generation path and compare the generated output with the specification's implicit OAuth security; done means the expected OAuth code is generated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, openapi, spring
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100