Skip to content

@SecurityScheme paramName not accounted for the name. #384

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.

Sign up for GitHub

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

Jump to bottom
Closed
lpandzic opened this issue Jan 28, 2020 · 0 comments
Closed

@SecurityScheme paramName not accounted for the name. #384

lpandzic opened this issue Jan 28, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@lpandzic
Copy link

The following:

@SecurityScheme(name = "BearerAuthCookie",
        type = SecuritySchemeType.APIKEY,
        in = SecuritySchemeIn.COOKIE,
        paramName = "JWT")

does not result into:

  securitySchemes:
    BearerAuthCookie:
      type: apiKey
      name: JWT
      in: cookie

and instead the name is set to BearerAuthCookie.
See https://github.com/swagger-api/swagger-core/blob/v2.0.4/modules/swagger-annotations/src/main/java/io/swagger/v3/oas/annotations/security/SecurityScheme.java#L71

Exact same issue as micronaut-projects/micronaut-openapi#59.
bnasslahsen pushed a commit that referenced this issue Jan 29, 2020
fixes ##384
564e88a
@bnasslahsen bnasslahsen added the enhancement New feature or request label Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lpandzic @bnasslahsen