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
Copy file name to clipboardExpand all lines: docs/specs/oauth-vendor-extension.yaml
+6-9Lines changed: 6 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,11 @@ openapi: 3.0.0
2
2
info:
3
3
title: Petstore API
4
4
description: |
5
-
Example to show how to use `x-client-id` and `x-client-secret` vendor extensions to pre fill them in the UI.
6
-
7
-
Below is the Open API spec snippet that shows its usage,
8
-
and if you check the authentication section you will find that client-id and client-secret is pre-filled, the user just needs to click on `GET TOKEN`
5
+
Example to show how to use `x-client-id`, `x-client-secret` and `x-default-scopes` vendor extensions to pre fill them in the UI.
6
+
7
+
Below is the Open API spec snippet that shows its usage,
8
+
and if you check the authentication section you will find that client-id and client-secret are pre-filled, the user just needs to click on `GET TOKEN`.
9
+
Also notice that the scope `dog-lover` is already checked
9
10
```yaml
10
11
openapi: 3.0.0
11
12
...
@@ -16,15 +17,14 @@ info:
16
17
type: oauth2
17
18
x-client-id: my-client-id # <--- when provided it will be pre filled in RapiDoc UI
18
19
x-client-secret: my-client-secret # <--- when provided it will be pre filled in RapiDoc UI
19
-
x-default-scopes: [dog-lover, another-one] # <--- when provided scopes will be pre checked in RapiDoc UI
20
+
x-default-scopes: [dog-lover] # <--- when provided scopes will be pre checked in RapiDoc UI
0 commit comments