Add support for spec-driven api-keys #6
Merged
Conversation
This file contains 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
Swagger-ui uses hard-coded `api_key` query-param for api-keys, with this commit, one can override this in the swagger spec - both key-name & in (header, query etc.) There are lot's of open issues related to this, without any resolution time-table. See: swagger-api/swagger-ui#1766 swagger-api/swagger-ui#1731 swagger-api/swagger-ui#1593
|
👍 |
ikitommi
added a commit
that referenced
this pull request
Nov 28, 2015
Add support for spec-driven api-keys
|
is there a way to use this from compojure-api? :swagger {:options {:ui {:authorizations {"api_key" {:name "authorization"
:in "header"}}}}} |
:swagger {:data {:security-definitions {"api_key" {:name "authorization"
:in "header"}}}If I recall correctly. This option is set in Swagger.json, not directly to swagger-ui. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Swagger-ui uses hard-coded
api_keyquery-param for api-keys,with this commit, one can override this in the swagger spec -
both key-name & in (header, query etc.) There are lot's of open
issues related to this, without any resolution time-table. See:
swagger-api/swagger-ui#1766
swagger-api/swagger-ui#1731
swagger-api/swagger-ui#1593