Skip to content

Commit 929a09a

Browse files
authored
Merge pull request openwallet-foundation#2046 from jfblier-amplitude/main
openwallet-foundation#2041 - Issue JSON-LD has invalid Admin API documentation
2 parents 29ace87 + fe61319 commit 929a09a

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

demo/AliceWantsAJsonCredential.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Also note that the above will only work with the `/issue-credential-2.0/create-o
3535

3636
Copy the "invitation" json text from the Faber shell and paste into the Alice shell to establish a connection between the two agents.
3737

38-
(If you are running with `--no-auto` you will also need to call the `/connections/accept-invitation` endpoint in alice's admin api swagger page.)
38+
(If you are running with `--no-auto` you will also need to call the `/connections/{conn_id}/accept-invitation` endpoint in alice's admin api swagger page.)
3939

4040
Now open up two browser windows to the [Faber](http://localhost:8021/api/doc) and [Alice](http://localhost:8031/api/doc) admin api swagger pages.
4141

@@ -82,7 +82,7 @@ Congradulations, you are now ready to start issuing JSON-LD credentials!
8282
- You have created a (non-public) DID for Faber to use to sign/issue the credentials - you will need to copy the DID that you created above into the examples below (as `issuer`).
8383
- You have created a (non-public) DID for Alice to use as her `credentialSubject.id` - this is required for Alice to sign the proof (the `credentialSubject.id` is not required, but then the provided presentation can't be verified).
8484

85-
To issue a credential, use the `/issue-credential-2.0/create-offer` endpoint. (You can also use the `/issue-credential-2.0/send`) endpoint, if, as mentioned above, you have included the `--no-auto` when starting both of the agents.)
85+
To issue a credential, use the `/issue-credential-2.0/send-offer` endpoint. (You can also use the `/issue-credential-2.0/send`) endpoint, if, as mentioned above, you have included the `--no-auto` when starting both of the agents.)
8686

8787
You can test with this example payload (just replace the "connection_id", "issuer" key, "credentialSubject.id" and "proofType" with appropriate values:
8888

@@ -336,7 +336,7 @@ In Alice's swagger page, submit the `/credentials/records/w3c` endpoint to see t
336336

337337
### Request Presentation Example
338338

339-
To request a proof, submit the following (with appropriate `connection_id`) to Faber's `/request-presentation-2.0/request-proof` endpoint:
339+
To request a proof, submit the following (with appropriate `connection_id`) to Faber's `/present-proof-2.0/send-request` endpoint:
340340

341341
```
342342
{
@@ -408,7 +408,7 @@ To request a proof, submit the following (with appropriate `connection_id`) to F
408408

409409
Note that the `is_holder` property can be used by Faber to verify that the holder of credential is the same as the subject of the attribute (`familyName`). Later on, the received presentation will be signed and verifiable only if `is_holder` with ` "directive": "required"` is included in the presentation request.
410410

411-
There are several ways that Alice can respond with a presentation. The simplest will just tell aca-py to put the presentation together and send it to Faber - submit the following to Alice's `/request-presentation-2.0/{pres_ex_id}/send-presentation`:
411+
There are several ways that Alice can respond with a presentation. The simplest will just tell aca-py to put the presentation together and send it to Faber - submit the following to Alice's `/present-proof-2.0/records/{pres_ex_id}/send-presentation`:
412412

413413
```
414414
{

0 commit comments

Comments
 (0)