-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relative URL for tokenUrl and authorizationUrl #557
Comments
It's undefined by the spec, so there's no clear answer there. I wouldn't rely on existing implementations to support that. We should clarify it in the next version. |
parent issue #585 |
Wording has been added to permit the use of URLs relative to the OpenAPI document, to match the behaviour of relative server URLs. Making the location of the security endpoints relative to the server (fka host+basePath) url is problematic now that we allow multiple servers and templated servers. |
Closing as resolved. |
How and where can i See token URL? |
It is not clear whether relative tokenUrl and authorizationUrl are authorized.
It would be great if we could set them as relative to host (or host+basePath ?). Or do you see an issue with that ?
The text was updated successfully, but these errors were encountered: