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
feat: align with draft13 and enable auth server integration (#2262)
* feat: align with draft13 and enable auth server integration
Signed-off-by: Ivan Wei <ivan.wei@ontario.ca>
* fix: lint and unit tests
Signed-off-by: Ivan Wei <ivan.wei@ontario.ca>
* fix: integration test
Signed-off-by: Ivan Wei <ivan.wei@ontario.ca>
* fix: code review
Signed-off-by: Ivan Wei <ivan.wei@ontario.ca>
---------
Signed-off-by: Ivan Wei <ivan.wei@ontario.ca>
Navigate to `http://localhost:3002` in your browser. You will start at the landing page. The sidebar has buttons to take you to the issuance and presentation pages.
37
+
Navigate to `http://localhost:3002` in your browser. You will start at the landing page. The sidebar has buttons to take you to the issuance and presentation pages.
38
38
39
39
1. Issue Credential
40
40
41
41
- This page generates a simple `UniversityCredential` for issuance
42
-
- The demo obscures and automates the necessary `credential-supported/create` call, which is what defines the type and values of a credential that can be issued
42
+
43
+
- The demo obscures and automates the necessary `credential-supported/create` call, which is what defines the type and values of a credential that can be issued
43
44
44
45
- Preparing a credential offer is simple:
45
-
- Enter your name and email, or use the test value provided, and hit `Register`
46
-
- Once you hit `Register`, you'll be automatically taken to the Credential Offer Page
46
+
- Enter your name and email, or use the test value provided, and hit `Register`
47
+
- Once you hit `Register`, you'll be automatically taken to the Credential Offer Page
47
48
48
49
2. Credential Offer Page
49
50
- Presents a credential offer in the form of a QR code.
@@ -164,13 +167,13 @@ admin ->> acapy: store presentation definition
164
167
admin -->> controller: created presentation definition
165
168
alice ->> controller: Hits web page initiating presentation
166
169
controller ->> admin: POST /oid4vp/request
167
-
admin ->> acapy: save request record associated <br/>with a particular pres def
170
+
admin ->> acapy: save request record associated <br/>with a particular pres def
168
171
admin -->> controller: request URI
169
172
controller ->> alice: QR Code
170
173
alice ->> holder: Scan QR Code
171
174
holder ->> public: GET /oid4vp/request/{request_id} (request uri in QR code)
172
175
public -> acapy: retrieve stored request
173
-
public -->> holder: request
176
+
public -->> holder: request
174
177
holder ->> public: POST /oid4vp/response/{presentation_id}
175
178
acapy ->> controller: POST /topic/oid4vp <br/>(state: presentation-valid/invalid)
176
179
controller ->> holder: result
@@ -183,26 +186,26 @@ controller ->> holder: result
183
186
The Plugin expects the following configuration options. These options can either be set by environment variable (`OID4VCI_*`) or by plugin config value (`-o oid4vci.*`).
184
187
185
188
-`OID4VCI_HOST` or `oid4vci.host`
186
-
- Host used for the OpenID4VCI public server
189
+
- Host used for the OpenID4VCI public server
187
190
-`OID4VCI_PORT` or `oid4vci.port`
188
-
- Port used for the OpenID4VCI public server
191
+
- Port used for the OpenID4VCI public server
189
192
-`OID4VCI_ENDPOINT` or `oid4vci.endpoint`
190
-
-`credential_issuer` endpoint, seen in the Credential Offer
193
+
-`credential_issuer` endpoint, seen in the Credential Offer
191
194
-`OID4VCI_CRED_HANDLER` or `oid4vci.cred_handler`
192
-
- Dict of credential handlers. e.g. `{"jwt_vc_json": "jwt_vc_json"}`
195
+
- Dict of credential handlers. e.g. `{"jwt_vc_json": "jwt_vc_json"}`
196
+
-`OID4VCI_AUTH_SERVER_URL` or `oid4vci.auth_server_url`
197
+
- Optional authorization server URL
198
+
-`OID4VCI_AUTH_SERVER_CLIENT` or `oid4vci.auth_server_client`
199
+
- Optional authorization server client credential, e.g. `{"auth_type": "client_secret_basic", "client_id": "client_id", "client_secret": "client_secret"}`
193
200
194
201
### Creating Supported Credential Records
195
202
196
203
To issue a credential using OpenID4VCI, the Issuer must first prepare credential issuer metadata including which credentials the Issuer can issue. Below is an example payload to the `POST /oid4vci/credential-supported/create/jwt` endpoint:
0 commit comments