Block Authorize button in API Catalog
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
Is your feature request related to a problem? Please describe.
Some customes are using Authorize button in API Catalog, but it's not working, and Swagger in Catalog will always use token from the session. Authorize button is confusing users.
Describe the solution you'd like
Block the Authorize button in API Catalog.
Describe alternatives you've considered
Hide the Authorize button in API Catalog.
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 locating the API Catalog UI and its Swagger Authorize control, then check how authentication is supplied from the session. Done means the Authorize button is blocked or hidden and the catalog continues using the session token without offering a misleading authorization flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100