-
Notifications
You must be signed in to change notification settings - Fork 341
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
Questions regarding swagger-ui and oauth #83
Comments
First of all, implicit flow is not implemented yet #4. Second of all, given that realm is set with |
Can you explain me how this config values are populated into the swagger-ui and how I can debug the authorization process? Is the authorization process within the function I mentioned above? BR |
@dhofstetter I am sorry, I have little time this month to answer questions in details. See the HTML on the Swagger UI page ( |
@dhofstetter Have you figured this out or you still need some help? |
I was able to do some workaround. Not a nice solution but works somehow! Do you plan to integrate swagger ui 3 someday? BR Daniel |
It would be helpful for others if you can share your workaround. There is also a chance that I will be able to help you to transform it to a proper solution.
From the user perspective, I don't see much value in Swagger-UI 3 now as it is still lacking the features I use in this example (OAuth2 Password Flow, JSON editor) noirbizarre/flask-restplus#267 (comment) |
I used a lot of your stuff for a current project, because your enhancements are just awesome!
But actually I'm unable to get everything working regarding the swagger-ui. The authorize button is going to be displayed as expected. And I get the list of defined scopes. But as soon as I want to get myself authorized for the swagger session there are two possibilities:
I also saw that you set the client_id and realm for swagger within your config, but I don't know where you are going to render them for usage within the swagger-ui.
Can you help me?
BR Daniel
The text was updated successfully, but these errors were encountered: