Skip to content

fix: swagger Authorize bearer steps (local 401) - #30

Merged
donkeyx merged 5 commits into
masterfrom
fix/swagger-bearer-auth-docs
Aug 10, 2026
Merged

donkeyx merged 5 commits into
masterfrom
fix/swagger-bearer-auth-docs

Conversation

@donkeyx

@donkeyx donkeyx commented Aug 10, 2026

Copy link
Copy Markdown
Owner

Swagger UI 401 with a correct token was often the duplicate Authorization
parameter (default Bearer with no token) fighting the Authorize dialog.

  • Remove extra @Param Authorization on secured ops
  • README: exact steps for local podman Bearer dev

Swagger was also generating an Authorization parameter defaulting to
"Bearer " which overwrote a good Authorize value. Rely on BearerAuth
only; document exact UI steps (Bearer dev, not just dev).
Default proxy GET url to https://httpbin.org/get (echoes headers/method).
Status 418, delay 2s, probe mode examples, clearer Authorize-only auth text.
Split proxy GET/POST handlers so Try it out does not send a body on GET
(browser fetch error). Refresh top swagger title/description for the
cluster-debug story. Default GET url remains httpbin.org/get.
@donkeyx
donkeyx merged commit 06c27bb into master Aug 10, 2026
2 of 3 checks passed
@donkeyx
donkeyx deleted the fix/swagger-bearer-auth-docs branch August 10, 2026 13:30

This branch was previously deployed

1 inactive deployment
ci — 5a021d1b Deployed Aug 10, 2026 by donkeyx via docker #71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant