Enable persistAuthorization for Swagger UI #204
Merged
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
From the docs: "If set to true, it persists authorization data and it would not be lost on browser close/refresh". https://swagger.io/docs/open-source-tools/swagger-ui/usage/configuration/
ulrikandersen
force-pushed
the
feature/swagger-ui-persist-authorization
branch
from
2284e7a to
d695605
Compare
Merged
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.
This PR enables
persistAuthorizationon Swagger UI which causes Swagger UI to remeber the credentals provided between reloads.This behavior is similar to the default behavior of Stoplight.
For both viewers the credentials are stored in local storage.