You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2023. It is now read-only.
The API discovery endpoint already contains information about which implicit scope is required for each endpoint:
However, in the corresponding html shown on the generated API docs doesn't show the required scope anywhere that I can see.
It would be nice to list out the scopes somewhere in the html to more easily determine which scopes are necessary to grant to an OAuth application for a specific use case. Thanks Quay!
The text was updated successfully, but these errors were encountered:
@brycefisher: That display comes from the Swagger UI, which is an open source tool found here: https://github.com/swagger-api/swagger-ui. If you update the tool to show the scopes in that display, then we can merge the changes. Otherwise, you can click on the Auth toggle (which says "off" in your screenshot), and it should show which scope is necessary.
Thanks for the speedy reply @josephschorr ! I wondered about that :-/
Clicking on the off pops up this modal, which displays the scopes required by the Swagger UI to run all of the examples; it does not indicate the minimum scopes required for that API endpoint. See screenshot:
I assume this piece is also generated from Swagger. Is that correct?
The API discovery endpoint already contains information about which implicit scope is required for each endpoint:
However, in the corresponding html shown on the generated API docs doesn't show the required scope anywhere that I can see.
It would be nice to list out the scopes somewhere in the html to more easily determine which scopes are necessary to grant to an OAuth application for a specific use case. Thanks Quay!
The text was updated successfully, but these errors were encountered: