swagger-api / swagger-api/swagger-ui
Oauth2 Authorization Code flow, can't log in after log out
Open
Nobody has claimed this yet.
cat: auth
needs: UX/design input
P2
type: bug
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Q&A (please complete the following information)
- OS: macOS
- Browser: chrome, safari
- Version: chrome 71.0, safari 11.1.2
- Method of installation: dist assets
- Swagger-UI version: 3.18.3
- Swagger/OpenAPI version: OpenAPI 3.0
Describe the bug you're encountering
It seems that log out functionality does not flushes authorization code received after successful Oauth2 log in. When you log out and logging in again token request sent again with the same code, not with the new one.
To reproduce...
- Authorize with Oauth2 Authorization Code flow
- Press Log Out
- Try to authorize again
Expected behavior
You can successfully log out and authorize again with Authorization Code flow
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 reproducing the issue in Swagger UI 3.18.3 using the OAuth2 Authorization Code flow, then inspect the authorization and Log Out entry points. Done means logging out and authorizing again successfully sends a new code rather than reusing the previous one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, openapi
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100