swagger-api / swagger-api/swagger-codegen

Spring Boot Bearer Token UI is not visible

Open
#8,331 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

I have created the Swagger API Through Swagger Hub with Security Definition as Bearer, i could clearly get all the components are visible clearly but when i exported and running as spring boot application, i could not see any configuration related to Bearer Header Token, I've Researched a lot regarding this issue but non of the could resolve this problem

Swagger-codegen version

Tested with Spring Boot 1.5.X and 2.X versions with Swagger 2.X
screenshot from 2018-06-18 18-17-41
screenshot from 2018-06-18 18-17-57
screenshot from 2018-06-19 10-01-32

Swagger declaration file content or url

Please find the Sample Swagger API on below location
https://app.swaggerhub.com/apis/JACK_Master/Sample-Jwt/1.0.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the Swagger Hub declaration at the linked URL in a generated Spring Boot application using the reported Spring Boot and Swagger 2.X versions. Compare the security definition with the generated UI and use the attached screenshots as the expected context. Done means the bearer-token configuration is visible and usable in the generated application.

Written by the indexing model from the issue text.

Assessment

Tech stack
spring-boot
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.