You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assuming the swagger endpoint is /swagger and
assuming you have relative OAuth2 configuration URLs, with relative URIs, V5.20 redirects to
"/swagger/identity/connect/authorize" on clicking the Authorize button. It ignores the relative "../" part from the url.
I did a few more experiments. If I look at the changes in 5.20, there were changes regarding url sanitization, so this might be a side effect of those.
./../ does not work
/../ works, but only if the path segment ../ points to root, as / anchors it to root
Q&A (please complete the following information)
Content & configuration
Swagger-UI configuration options:
Describe the bug you're encountering
Assuming the swagger endpoint is /swagger and
assuming you have relative OAuth2 configuration URLs, with relative URIs, V5.20 redirects to
"/swagger/identity/connect/authorize" on clicking the Authorize button. It ignores the relative "../" part from the url.
Example:
https://localhost/swagger with swagger json on https://localhost/swagger/v1/swagger.json, then the above configuration redirects to: https://localhost/swagger/identity/connect/authorize, instead of https://localhost/identity/connect/authorize.
To reproduce...
Steps to reproduce the behavior:
Configure relative OAuth2 security scheme as above, with any given swagger config and click Authorize
Expected behavior
It redirects to "/identity/connect/authorize"
Additional context or thoughts
This works in 5.19.
this was found in Swashbuckle for .NET and repro'd to be the UI change
domaindrivendev/Swashbuckle.AspNetCore#3287
The text was updated successfully, but these errors were encountered: