Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openapi-generator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,476
    • Issues 3,476
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 402
    • Merge requests 402
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenAPI Tools
  • openapi-generator
  • Issues
  • #7904
Closed
Open
Issue created Nov 09, 2020 by Administrator@rootContributor5 of 6 checklist items completed5/6 checklist items

[BUG] [rust-server] API token in query is not parsed with correct parameter name

Created by: N-Schaef

Bug Report Checklist

  • Have you provided a full/minimal spec to reproduce the issue?
  • Have you validated the input using an OpenAPI validator (example)?
  • Have you tested with the latest master to confirm the issue still exists?
  • Have you searched for related issues/PRs?
  • What's the actual output vs expected output?
  • [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description

If one uses the apiKeysecurity scheme with in: query, then the parameter name is ignored. It will always be "api_key_query".

openapi-generator version

5.0.0-SNAPSHOT (eceac6a6)

OpenAPI declaration file content or url
openapi: "3.0.2"
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: query
      name: api-token
info:
  title: Test
  version: "1"
paths:
  /:
    get:
      responses: 
        '200':
          description: OK    
Generation Details
docker run --rm -v "$DIR/..:/local" openapitools/openapi-generator-cli generate \
    -i /local/openapi/main.yaml \
    -g rust-server \
    -o /local/out 
Steps to reproduce
  • Generate Stubs
  • Add code to check context for AuthData
  • GET endpoint with localhost:8080/1/?api-token=abc

Now no AuthData exists in the context, but it should be. If instead localhost:8080/1/?api_key_query=abc is used, the auth data exists

Related issues/PRs

Will open PR in a few minutes and update.

Assignee
Assign to
Time tracking