swagger-api / swagger-api/swagger-ui
Swagger authorization does not complet against Microsoft Entra ID on Chrome and Edge
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
- OS: Windows 10
- Browser: Edge,Chrome, Firefox
- Swagger-UI version: 6.5.0
- Swagger/OpenAPI version: 6.5.0
Hi,
I have a ASP.NET Core Web API with Swagger and the authorization happens via Microsoft Entra ID.
This is working but only on Firefox. When I click Authorization button in Swagger-UI the Edge and Chrome browsers are keep waiting for something but nothing happens.
CORS is enabled: policy.AllowAnyOrigin().AllowAnyHeader().AllowAnyMethod();
Swagger registration redirectURL is https://localhost:7215/swagger/oauth2-redirect.html
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 Swagger UI Authorization-button flow with Microsoft Entra ID at the reported oauth2-redirect.html URL in Edge and Chrome, then compare it with Firefox. Trace the OAuth redirect and browser behavior to identify where the flow remains waiting; done means authorization completes consistently in the affected browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100