Support additional query parameters during OAuth2 authorization process #1648
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…th2 authorization process
Contributor
Author
|
Hi, |
fehguy
added a commit
that referenced
this pull request
Dec 9, 2015
Support additional query parameters during OAuth2 authorization process
Jonahss
pushed a commit
to eaze/swagger-ui
that referenced
this pull request
Aug 12, 2016
Support additional query parameters during OAuth2 authorization process
vincent-zurczak
pushed a commit
to roboconf/swagger-ui
that referenced
this pull request
Aug 19, 2016
Support additional query parameters during OAuth2 authorization process
JuanSW18
pushed a commit
to Digital-Paw/digital-paw-swagger-ui
that referenced
this pull request
Aug 23, 2024
Support additional query parameters during OAuth2 authorization process
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, while trying to integrate an Azure Active Directory (AAD) protected API with Swagger-UI I encountered the issue where it is required to specify the "Resource" parameter but there was no way of easily providing it. This problem is covered in the open issue #1302.
I made a generic mechanism for passing custom parameters (instead of adding a specific "Resource" parameter) since I also really needed a custom parameter "domain_hint" as explained here - http://www.cloudidentity.com/blog/2014/11/17/skipping-the-home-realm-discovery-page-in-azure-ad/.
I'd appreciate it if this addition can be merged into Swagger-UI. Thanks!