-
Notifications
You must be signed in to change notification settings - Fork 303
OAuth2 Scopes do not render #235
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
Comments
Not sure of what you are expecting in the UI. |
thats not for more info refer to #200 on how RapiDoc shows them |
I already have defined security:
- Bearer:
- write:domain
- admin
- OAuth2:
- write:domain
- admin and components:
securitySchemes:
Bearer:
type: apiKey
description: |
Bearer scheme uses static perpetual token and is less secure.
Token has a `write:domain` or `admin` permission associated with it.
It determines whether you are authorized to invoke a particular operation or not.
in: header
name: Authorization
OAuth2:
type: oauth2
description: |
OAuth2 scheme is a safer and more secure way to give you access with a short-lived token.
flows:
clientCredentials:
tokenUrl: https://...../oauth2/token
scopes:
'write:domain': Manage Services and Subscribers in your Domain
admin: Manage Services and Subscribers in all Domains I would be nice to see what authorizations are available at the individual operation level (which either inherits from global |
It does show up in the top right corner of the each operation but it doesn't contain scope information which could be overridden at the operation level by defining |
I don't know if it's a missing features or a bug but OAuth2 scopes don't show up. See
Security
section in the yaml.The text was updated successfully, but these errors were encountered: