From dd87af2428caec910aa1c83a12845ef0ccabad6c Mon Sep 17 00:00:00 2001
From: Georgi Michev <georgi.michev@vereign.com>
Date: Fri, 16 Feb 2024 17:57:23 +0200
Subject: [PATCH] Update documentation reference tags
Signed-off-by: Georgi Michev <georgi.michev@vereign.com>
---
.../features/tsa/signer/v1/credential/proof/POST.feature | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/src/test/resources/features/tsa/signer/v1/credential/proof/POST.feature b/src/test/resources/features/tsa/signer/v1/credential/proof/POST.feature
index 8b48c20b..8f810a28 100644
--- a/src/test/resources/features/tsa/signer/v1/credential/proof/POST.feature
+++ b/src/test/resources/features/tsa/signer/v1/credential/proof/POST.feature
@@ -22,7 +22,7 @@ Feature: API - TSA - Signer credential proof - v1/credential/proof POST
| alumni of | for_proof_alumni | Signer_CredentialProof_alumni_schema.json |
| without ID | for_proof_without_ID | Signer_CredentialProof_without_ID_schema.json |
- @phase2 @IDM.TSA.E1.00005 @IDM.TSA.E1.00006
+ @phase2 @IDM.TSA.E1.00005 @IDM.TSA.E1.00006 @IDM.TSA.E1.00019
Scenario: TSA - create two consecutive proofs - Positive
When I load the REST request {Credential.json} with profile {for_proof_with_02_proof}
And I create credential proof via TSA Signer API
@@ -31,21 +31,21 @@ Feature: API - TSA - Signer credential proof - v1/credential/proof POST
And the field {proof[1].verificationMethod} contains the value {did:web:vault.vereign.com:tsa:policy:policy:policies:example:returnDID:1.0:evaluation#key1}
And the field {proof[2].verificationMethod} contains the value {did:web:vault.vereign.com:tsa:policy:policy:policies:example:returnDID:1.0:evaluation#key1}
- @negative @phase2 @IDM.TSA.E1.00005 @IDM.TSA.E1.00006
+ @negative @phase2 @IDM.TSA.E1.00005 @IDM.TSA.E1.00006 @IDM.TSA.E1.00019
Scenario: TSA - create two consecutive proofs with modified issuance date - Negative
When I load the REST request {Credential.json} with profile {for_proof_with_modified_second_proof_date}
And I create credential proof via TSA Signer API
Then the status code should be {403}
And the field {message} contains the value {invalid signature}
- @negative @phase2 @IDM.TSA.E1.00005 @IDM.TSA.E1.00006
+ @negative @phase2 @IDM.TSA.E1.00005 @IDM.TSA.E1.00006 @IDM.TSA.E1.00019
Scenario: TSA - create two consecutive proofs with modified credential subject ID - Negative
When I load the REST request {Credential.json} with profile {for_proof_with_modified_second_proof_cred_subject}
And I create credential proof via TSA Signer API
Then the status code should be {403}
And the field {message} contains the value {invalid signature}
- @negative @phase2 @IDM.TSA.E1.00005 @IDM.TSA.E1.00006
+ @negative @phase2 @IDM.TSA.E1.00005 @IDM.TSA.E1.00006 @IDM.TSA.E1.00019
Scenario: TSA - create two consecutive proofs with modified credential subject allow - Negative
When I load the REST request {Credential.json} with profile {for_proof_with_modified_second_proof_cred_subject_allow}
And I create credential proof via TSA Signer API
--
GitLab