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: api/api.yaml
+69-3Lines changed: 69 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,26 @@ tags:
10
10
description: All api-endpoints, e.g. the once that can be reused by other applications
11
11
12
12
paths:
13
+
/api/v1/authorization:
14
+
get:
15
+
tags:
16
+
- api
17
+
parameters:
18
+
- $ref: '#/components/parameters/QueryState'
19
+
- $ref: '#/components/parameters/ClientId'
20
+
- $ref: '#/components/parameters/RedirectUri'
21
+
- $ref: '#/components/parameters/RequestUri'
22
+
- $ref: '#/components/parameters/Scope'
23
+
- $ref: '#/components/parameters/Nonce'
24
+
- $ref: '#/components/parameters/ResponseType'
25
+
operationId: AuthorizationEndpoint
26
+
summary: OAuth-2 compliant authorization endpoint, to provide the correct redirect
27
+
description: Endpoint to be used as entry for the authorization process, providing the redirect to the concrete authorization method.
28
+
In case a request_uri provides access to an request object, all mandatory parameters can also be provided as part of that object.
29
+
responses:
30
+
'302':
31
+
description: A redirect to the authorization entrypoint.
32
+
13
33
/api/v2/loginQR:
14
34
get:
15
35
tags:
@@ -97,6 +117,9 @@ paths:
97
117
parameters:
98
118
- $ref: '#/components/parameters/QueryState'
99
119
- $ref: '#/components/parameters/ClientId'
120
+
- $ref: '#/components/parameters/Scope'
121
+
- $ref: '#/components/parameters/RequestMode'
122
+
- $ref: '#/components/parameters/RedirectPath'
100
123
operationId: StartSIOPSameDevice
101
124
summary: Starts the siop flow for credentials hold by the same device
102
125
description: When the credential is already present in the requesting browser, the same-device flow can be used. It creates the login information and then redirects to the /authenticationresponse path.
@@ -153,7 +176,6 @@ paths:
153
176
responses:
154
177
'204':
155
178
description: Ok when it worked
156
-
157
179
/token:
158
180
post:
159
181
tags:
@@ -302,6 +324,14 @@ components:
302
324
schema:
303
325
type: string
304
326
example: https://my-app.com/request.jwt
327
+
RedirectPath:
328
+
name: redirect_path
329
+
description: If no redirect path is provided, an 'oid4vp' deeplink will be returned
description: Same uri as provided as callback in the original request.
611
649
example: https://my-portal.com/auth_callback
650
+
resource:
651
+
type: string
652
+
format: uri
653
+
description: A URI that indicates the target service or resource where the client intends to use the requested security token. Resource
654
+
is ignored if the target client is provided as path parameter
655
+
audience:
656
+
type: string
657
+
description: The logical name of the target service where the client intends to use the requested security token.
658
+
scope:
659
+
type: array
660
+
items:
661
+
type: string
662
+
description: A list of space-delimited, case-sensitive strings, that allow the client to specify the desired scope of the requested security token in the context of the service or resource where the token will be used.
663
+
requested_token_type:
664
+
type: string
665
+
description: An identifier, for the type of the requested security token.
// When set, the claim are flatten to plain JWT-claims before beeing included, instead of keeping the credential/presentation structure, where the claims are under the key vc or vp
// A non-empty array of objects that specifies claims in the requested Credential. Verifiers MUST NOT point to the same claim more than once in a single query. Wallets SHOULD ignore such duplicate claim queries.
// Defines additional properties requested by the Verifier that apply to the metadata and validity data of the Credential. The properties of this object are defined per Credential Format. If empty, no specific constraints are placed on the metadata or validity of the requested Credential.
0 commit comments