From d8417e8539b105b2b7026702bc9b8d168d360f21 Mon Sep 17 00:00:00 2001 From: supersonicwisd1 Date: Sat, 13 Apr 2024 11:35:11 +0100 Subject: [PATCH 1/6] vc-di into aca-py docs Signed-off-by: supersonicwisd1 --- docs/features/W3cCredentials.md | 91 +++++++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 docs/features/W3cCredentials.md diff --git a/docs/features/W3cCredentials.md b/docs/features/W3cCredentials.md new file mode 100644 index 0000000000..2fbf9561b5 --- /dev/null +++ b/docs/features/W3cCredentials.md @@ -0,0 +1,91 @@ +## Verifiable Credential Data Integrity (VC-DI) Credentials in Aries Cloud Agent Python (ACA-Py) + +This document outlines a new functionality within Aries Agent that facilitates the issuance of credentials and presentations in compliance with the W3C standard. + +### Table of Contents + +- [General Concept](#general-concept) +- [Prerequisites](#prerequisites) + - [Verifiable Credentials Data Model](#verifiable-credentials-data-model) + - [Verifiable Presentations Data Model](#verifiable-presentations-data-model) + - [DIF Presentation Format](#dif-presentation-format) +- [Preparing to Issue a Credential](#preparing-to-issue-a-credential) + - [VC-DI Context](#vc-di-context) + - [Signature Suite](#signature-suite) + - [DID Method](#did-method) +- [Issue a Credential](#issue-a-credential) + +### General Concept + +The introduction of VC-DI credentials in ACA-Py facilitates the issuance of credentials and presentations in adherence to the W3C standard. + +### Prerequisites + +Before utilizing this feature, it is essential to have the following: + +#### Verifiable Credentials Data Model + +A basic understanding of the Verifiable Credentials Data Model is required. Resources for reference include: + +- [Verifiable Credentials Data Model](https://www.w3.org/TR/vc-data-model/) + +#### Verifiable Presentations Data Model + +Familiarity with the Verifiable Presentations Data Model is necessary. Relevant resources can be found at: + +- [Verifiable Presentations Data Model](https://www.w3.org/TR/vc-data-model/#presentations) + +#### DIF Presentation Format + +Understanding the DIF Presentation Format is recommended. Access resources at: + +- [DIF Presentation Format](https://identity.foundation/presentation-exchange/) + +### Preparing to Issue a Credential + +To prepare for credential issuance, the following steps must be taken: + +#### VC-DI Context + +Ensure that every property key in the document is mappable to an IRI. This requires either the property key to be an IRI by default or to have the shorthand property mapped in the `@context` of the document. + +```json +{ + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2", + { + "@vocab": "https://www.w3.org/ns/credentials/issuer-dependent#" + } + ] +} +``` + +#### Signature Suite + +Select a signature suite for use. VC-DI format currently supports EdDSA signature suites for issuing credentials. + +- [`Ed25519Signature2020`](https://w3c.github.io/vc-di-eddsa/#ed25519signature2020-0) + +#### DID Method + +Choose a DID method for issuing the credential. VC-DI format currently supports the `did:key` method. + +##### `did:key` + +A `did:key` did is not anchored to a ledger, but embeds the key directly in the identifier part of the did. See the [did:key Method Specification](https://w3c-ccg.github.io/did-method-key/) for more information. + +You can create a `did:key` using the `/wallet/did/create` endpoint with the following body. + +```jsonc +{ + "method": "key", + "options": { + "key_type": "ed25519" + } +} +``` + +### Issue a Credential + +The issuance of W3C credentials is facilitated through the `/issue-credential-2.0/send` endpoint. This process adheres to the formats described in [RFC 0809 VC-DI](https://github.com/hyperledger/aries-rfcs/blob/main/features/0809-w3c-data-integrity-credential-attachment/README.md) and utilizes `didcomm` for communication between agents. \ No newline at end of file From 9bb51b6da57ce7409061a0950b00116d2c6e22b4 Mon Sep 17 00:00:00 2001 From: supersonicwisd1 Date: Tue, 16 Jul 2024 13:25:09 +0100 Subject: [PATCH 2/6] docs: updating the w3c format docs Signed-off-by: supersonicwisd1 --- docs/features/W3cCredentials.md | 538 +++++++++++++++++++++++++++++++- 1 file changed, 537 insertions(+), 1 deletion(-) diff --git a/docs/features/W3cCredentials.md b/docs/features/W3cCredentials.md index 2fbf9561b5..87b0466f6a 100644 --- a/docs/features/W3cCredentials.md +++ b/docs/features/W3cCredentials.md @@ -14,6 +14,14 @@ This document outlines a new functionality within Aries Agent that facilitates t - [Signature Suite](#signature-suite) - [DID Method](#did-method) - [Issue a Credential](#issue-a-credential) +- [Verify a Credential](#verify-a-credential) +- [Present Proof](#present-proof) + - [Requesting Proof](#requesting-proof) + - [Presenting Proof](#presenting-proof) + - [Verifying Proof](#verifying-proof) +- [Appendix](#appendix) + - [Glossary of Terms](#glossary-of-terms) + - [References and Resources](#references-and-resources) ### General Concept @@ -88,4 +96,532 @@ You can create a `did:key` using the `/wallet/did/create` endpoint with the foll ### Issue a Credential -The issuance of W3C credentials is facilitated through the `/issue-credential-2.0/send` endpoint. This process adheres to the formats described in [RFC 0809 VC-DI](https://github.com/hyperledger/aries-rfcs/blob/main/features/0809-w3c-data-integrity-credential-attachment/README.md) and utilizes `didcomm` for communication between agents. \ No newline at end of file +The issuance of W3C credentials is facilitated through the `/issue-credential-2.0/send` endpoint. This process adheres to the formats described in [RFC 0809 VC-DI](https://github.com/hyperledger/aries-rfcs/blob/main/features/0809-w3c-data-integrity-credential-attachment/README.md) and utilizes `didcomm` for communication between agents. + +To issue a W3C credential, follow these steps: + +1. **Prepare the Credential Data:** +Ensure the credential data conforms to the VC-DI context. + +
+JSON example + +```jsonc +{ + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2", + { + "@vocab": "https://www.w3.org/ns/credentials/issuer-dependent#" + } + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } +} +``` +
+ +2. **Send the Credential:** +Use the `/issue-credential-2.0/send` endpoint to issue the credential. + +
+JSON example + +```jsonc +{ + "auto_issue": true, + "auto_remove": false, + "comment": "Issuing a test credential", + "credential_preview": { + "@type": "https://didcomm.org/issue-credential/2.0/credential-preview", + "attributes": [ + {"name": "name", "value": "John Doe"} + ] + }, + "trace": false +} +``` +
+ +3. **Verify the Response:** +The response should confirm the credential issuance. + +
+JSON example + +```jsonc +{ + "state": "credential_issued", + "credential_id": "12345", + "thread_id": "abcde", + "role": "issuer" +} +``` +
+ +### Verify a Credential + +To verify a credential, follow these steps: + +1. **Prepare the Verification Request:** +Ensure the request conforms to the verification context. + +
+JSON example + +```jsonc +{ + "verifiableCredential": [ + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } + ] +} +``` +
+ +2. **Send the Verification Request:** +Use the `/verifier-credential/2.0/verify` endpoint. + +
+JSON example + +```jsonc +{ + "presentation": { + "verifiableCredential": [ + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } + ] + } +} +``` +
+ +3. **Verify the Response:** +The response should confirm the credential verification. + +
+JSON example + +```jsonc +{ + "verified": true, + "presentation": { + "type": "VerifiablePresentation", + "verifiableCredential": [ + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } + ], + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "authentication", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } +} +``` +
+ +### Present Proof + +#### Requesting Proof + +To request proof, follow these steps: + +1. **Prepare the Proof Request:** + Ensure the request aligns with the DIF Presentation Format. + +
+ JSON example + + ```jsonc + { + "presentation_definition": { + "id": "example-presentation-definition", + "input_descriptors": [ + { + "id": "example-input-descriptor", + "schema": [ + { + "uri": "https://www.w3.org/2018/credentials/v1" + } + ], + "constraints": { + "fields": [ + { + "path": ["$.credentialSubject.name"], + "filter": { + "type": "string", + "pattern": "John Doe" + } + } + ] + } + } + ] + } + } + ``` +
+ +2. **Send the Proof Request:** + Use the `/present-proof-2.0/request-presentation` endpoint. + +
+ JSON example + + ```jsonc + { + "comment": "Requesting proof of name", + "presentation_request": { + "presentation_definition": { + "id": "example-presentation-definition", + "input_descriptors": [ + { + "id": "example-input-descriptor", + "schema": [ + { + "uri": "https://www.w3.org/2018/credentials/v1" + } + ], + "constraints": { + "fields": [ + { + "path": ["$.credentialSubject.name"], + "filter": { + "type": "string", + "pattern": "John Doe" + } + } + ] + } + } + ] + } + } + } + ``` +
+ +3. **Verify the Response:** + The response should confirm the proof request. + +
+JSON example + + ```jsonc + { + "state": "presentation_received", + "thread_id": "abcde", + "role": "verifier" + } + ``` +
+ +#### Presenting Proof + +To present proof, follow these steps: + +1. **Prepare the Presentation Data:** + Ensure the presentation data conforms to the VC-DI context. + +
+ JSON example + + ```jsonc + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiablePresentation"], + "verifiableCredential": [ + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } + ] + } + ``` +
+ +2. **Send the Presentation:** + Use the `/present-proof-2.0/present-presentation` endpoint. + +
+ JSON example + + ```jsonc + { + "presentation": { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiablePresentation"], + "verifiableCredential": [ + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } + ] + }, + "comment": "Presenting proof of name" + } + ``` +
+ +3. **Verify the Response:** + The response should confirm the presentation. + +
+ JSON example + + ```jsonc + { + "state": "presentation_sent", + "thread_id": "abcde", + "role": "prover" + } + ``` +
+ +#### Verifying Proof + +To verify presented proof, follow these steps: + +1. **Prepare the Verification Data:** + Ensure the verification data aligns with the VC-DI context. + +
+ JSON example + + ```jsonc + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiablePresentation"], + "verifiableCredential": [ + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } + ] + } + ``` +
+ +2. **Send the Verification Request:** + Use the `/verifier-proof-2.0/verify` endpoint. + +
+ JSON example + + ```jsonc + { + "presentation": { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiablePresentation"], + "verifiableCredential": [ + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } + ] + } + } + ``` +
+ +3. **Verify the Response:** + The response should confirm the proof verification. + +
+ JSON example + + ```jsonc + { + "verified": true, + "presentation": { + "type": "VerifiablePresentation", + "verifiableCredential": [ + { + "@context": [ + "https://www.w3.org/2018/credentials/v1", + "https://w3id.org/security/data-integrity/v2" + ], + "type": ["VerifiableCredential"], + "issuer": "did:key:z6MkqG......", + "issuanceDate": "2023-01-01T00:00:00Z", + "credentialSubject": { + "id": "did:key:z6Mkh......", + "name": "John Doe" + }, + "proof": { + "type": "Ed25519Signature2020", + "created": "2023-01-01T00:00:00Z", + "proofPurpose": "assertionMethod", + "verificationMethod": "did:key:z6MkqG......#z6MkqG......", + "jws": "eyJhbGciOiJFZERTQSJ9..." + } + } + ] + } + } + ``` +
+ +### Appendix + +#### Glossary of Terms + +- **VC-DI:** Verifiable Credential Data Integrity +- **W3C:** World Wide Web Consortium +- **DID:** Decentralized Identifier +- **EdDSA:** Edwards-curve Digital Signature Algorithm +- **DIF:** Decentralized Identity Foundation + +#### References and Resources + +- [Aries Cloud Agent Python Documentation](https://github.com/hyperledger/aries-cloudagent-python) +- [Verifiable Credentials Data Model](https://www.w3.org/TR/vc-data-model/) +- [Verifiable Presentations Data Model](https://www.w3.org/TR/vc-data-model/#presentations) +- [DIF Presentation Format](https://identity.foundation/presentation-exchange/) +- [did:key Method Specification](https://w3c-ccg.github.io/did-method-key/) \ No newline at end of file From 06d00ed69dfcfd1a5ed0bb8c995dc73090d11778 Mon Sep 17 00:00:00 2001 From: supersonicwisd1 Date: Fri, 19 Jul 2024 13:14:19 +0100 Subject: [PATCH 3/6] update on the vcdi doc Signed-off-by: supersonicwisd1 --- docs/features/W3cCredentials.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/docs/features/W3cCredentials.md b/docs/features/W3cCredentials.md index 87b0466f6a..5ff03e368c 100644 --- a/docs/features/W3cCredentials.md +++ b/docs/features/W3cCredentials.md @@ -133,7 +133,12 @@ Ensure the credential data conforms to the VC-DI context. ``` -2. **Send the Credential:** +2. **Select Credential type** +The ability to choose the credential type (indy, vc_di) to be issued. The credential type is used to determine the schema for the credential data. + +The format to change credential can be seen ["Demo Instruction"](https://github.com/sarthakvijayvergiya/aries-cloudagent-python/blob/whatscookin/feat/vc-di-proof/docs/demo/README.md) + +3. **Send the Credential:** Use the `/issue-credential-2.0/send` endpoint to issue the credential.
@@ -155,7 +160,7 @@ Use the `/issue-credential-2.0/send` endpoint to issue the credential. ```
-3. **Verify the Response:** +4. **Verify the Response:** The response should confirm the credential issuance.
@@ -624,4 +629,5 @@ To verify presented proof, follow these steps: - [Verifiable Credentials Data Model](https://www.w3.org/TR/vc-data-model/) - [Verifiable Presentations Data Model](https://www.w3.org/TR/vc-data-model/#presentations) - [DIF Presentation Format](https://identity.foundation/presentation-exchange/) -- [did:key Method Specification](https://w3c-ccg.github.io/did-method-key/) \ No newline at end of file +- [did:key Method Specification](https://w3c-ccg.github.io/did-method-key/) +- ["Aries Cloud Agent Python (ACA-Py) Demos"](https://github.com/sarthakvijayvergiya/aries-cloudagent-python/blob/whatscookin/feat/vc-di-proof/docs/demo/README.md) \ No newline at end of file From ca0fd6de183055f83c30f5ca72c87c2788d87e7e Mon Sep 17 00:00:00 2001 From: supersonicwisd1 Date: Fri, 19 Jul 2024 13:15:28 +0100 Subject: [PATCH 4/6] update on the vcdi doc Signed-off-by: supersonicwisd1 --- docs/features/W3cCredentials.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/W3cCredentials.md b/docs/features/W3cCredentials.md index 5ff03e368c..cb1f3a4daa 100644 --- a/docs/features/W3cCredentials.md +++ b/docs/features/W3cCredentials.md @@ -136,7 +136,7 @@ Ensure the credential data conforms to the VC-DI context. 2. **Select Credential type** The ability to choose the credential type (indy, vc_di) to be issued. The credential type is used to determine the schema for the credential data. -The format to change credential can be seen ["Demo Instruction"](https://github.com/sarthakvijayvergiya/aries-cloudagent-python/blob/whatscookin/feat/vc-di-proof/docs/demo/README.md) +The format to change credential can be seen in the ["Demo Instruction"](https://github.com/sarthakvijayvergiya/aries-cloudagent-python/blob/whatscookin/feat/vc-di-proof/docs/demo/README.md) 3. **Send the Credential:** Use the `/issue-credential-2.0/send` endpoint to issue the credential. From 7b89d6e03c825de69cf4f9361f23b040a3149ff5 Mon Sep 17 00:00:00 2001 From: supersonicwisd1 Date: Fri, 19 Jul 2024 23:51:06 +0100 Subject: [PATCH 5/6] resolve: updated vcdi doc Signed-off-by: supersonicwisd1 --- docs/demo/README.md | 3 +++ docs/features/W3cCredentials.md | 33 +++++++++++++++++++-------------- 2 files changed, 22 insertions(+), 14 deletions(-) diff --git a/docs/demo/README.md b/docs/demo/README.md index 86184cd692..cb74069b9b 100644 --- a/docs/demo/README.md +++ b/docs/demo/README.md @@ -172,6 +172,7 @@ Faber: ``` (1) Issue Credential + (1a) Set Credential Type (indy) (2) Send Proof Request (3) Send Message (4) Create New Invitation @@ -225,6 +226,7 @@ Faber will setup support for revocation automatically, and you will see an extra ``` (1) Issue Credential + (1a) Set Credential Type (indy) (2) Send Proof Request (3) Send Message (4) Create New Invitation @@ -321,6 +323,7 @@ Faber: ``` (1) Issue Credential + (1a) Set Credential Type (indy) (2) Send Proof Request (3) Send Message (4) Create New Invitation diff --git a/docs/features/W3cCredentials.md b/docs/features/W3cCredentials.md index cb1f3a4daa..66f48fdebe 100644 --- a/docs/features/W3cCredentials.md +++ b/docs/features/W3cCredentials.md @@ -127,7 +127,7 @@ Ensure the credential data conforms to the VC-DI context. "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ``` @@ -155,6 +155,11 @@ Use the `/issue-credential-2.0/send` endpoint to issue the credential. {"name": "name", "value": "John Doe"} ] }, + "filter": { + "format": { + "cred_def_id": "FMB5MqzuhR..." + } + }, "trace": false } ``` @@ -206,7 +211,7 @@ Ensure the request conforms to the verification context. "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ] @@ -215,7 +220,7 @@ Ensure the request conforms to the verification context.
2. **Send the Verification Request:** -Use the `/verifier-credential/2.0/verify` endpoint. +Use the `/present-proof/send-request` endpoint.
JSON example @@ -241,7 +246,7 @@ Use the `/verifier-credential/2.0/verify` endpoint. "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ] @@ -279,7 +284,7 @@ The response should confirm the credential verification. "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ], @@ -288,7 +293,7 @@ The response should confirm the credential verification. "created": "2023-01-01T00:00:00Z", "proofPurpose": "authentication", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } } @@ -338,7 +343,7 @@ To request proof, follow these steps:
2. **Send the Proof Request:** - Use the `/present-proof-2.0/request-presentation` endpoint. + Use the `/present-proof-2.0/send-request` endpoint.
JSON example @@ -426,7 +431,7 @@ To present proof, follow these steps: "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ] @@ -435,7 +440,7 @@ To present proof, follow these steps:
2. **Send the Presentation:** - Use the `/present-proof-2.0/present-presentation` endpoint. + Use the `/present-proof-2.0/send-request` endpoint.
JSON example @@ -466,7 +471,7 @@ To present proof, follow these steps: "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ] @@ -526,7 +531,7 @@ To verify presented proof, follow these steps: "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ] @@ -535,7 +540,7 @@ To verify presented proof, follow these steps:
2. **Send the Verification Request:** - Use the `/verifier-proof-2.0/verify` endpoint. + Use the `/present-proof-2.0/send-request` endpoint.
JSON example @@ -566,7 +571,7 @@ To verify presented proof, follow these steps: "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ] @@ -604,7 +609,7 @@ To verify presented proof, follow these steps: "created": "2023-01-01T00:00:00Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkqG......#z6MkqG......", - "jws": "eyJhbGciOiJFZERTQSJ9..." + "proofValue": "eyJhbGciOiJFZERTQSJ9..." } } ] From 9007d97dba22a3593dbc45b8ca72a4e069c4e055 Mon Sep 17 00:00:00 2001 From: supersonicwisd1 Date: Fri, 19 Jul 2024 23:55:33 +0100 Subject: [PATCH 6/6] resolve: changed demo link to relative link Signed-off-by: supersonicwisd1 --- docs/features/W3cCredentials.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/W3cCredentials.md b/docs/features/W3cCredentials.md index 66f48fdebe..c0a6441a94 100644 --- a/docs/features/W3cCredentials.md +++ b/docs/features/W3cCredentials.md @@ -136,7 +136,7 @@ Ensure the credential data conforms to the VC-DI context. 2. **Select Credential type** The ability to choose the credential type (indy, vc_di) to be issued. The credential type is used to determine the schema for the credential data. -The format to change credential can be seen in the ["Demo Instruction"](https://github.com/sarthakvijayvergiya/aries-cloudagent-python/blob/whatscookin/feat/vc-di-proof/docs/demo/README.md) +The format to change credential can be seen in the ["Demo Instruction"](../demo/README.md) 3. **Send the Credential:** Use the `/issue-credential-2.0/send` endpoint to issue the credential.