Merge branch 'feature/proof-manager' into 'develop'

Proof Manager BDD

See merge request !4

features/proof/findProofByPresentationId.feature

+Feature: Get Proof Presentation By Id
+        Return the single proof presentation details
+
+Scenario: Provide valid presentation id
+    Given The presentation id is available on agent database.
+    When  provide valid presentation id.
+    Then  should return proof presentation details.
+
+Scenario: Provide invalid presentation id
+    Given The presentation id available.
+    When  provide invalid presentation id.
+    Then  should return no data found with status code 404.
+
+Scenario: Provide validated page and pageSize
+    Given proof presentation data available on OCM database. 
+    When  passed valid page.
+    And   passed valid pageSize.
+    Then  should get proof presentation list.
+
+Scenario: Provide validated page and pageSize
+    Given proof presentation data is not available on OCM database.
+    When  passed valid page.
+    And   passed valid pageSize.
+    Then  should get http status 404.
+    
+Scenario: Not provide a presentation id
+    Given The presentation id available.
+    When  not provide presentation id.
+    Then  should return presentation request required following attributes ( presentation_id ) with status code 400.
\ No newline at end of file

features/proof/sendOutOfBandPresentationRequest.feature

+As a OCM Admin 
+    I want to verify credentials without connection.
+
+Scenario: OCM admin verify credentials
+    Given PCM user should hold credentials in there wallet.
+    When  OCM verifer orgnization sends a proof presentation request with following fields ( schemaId or credentialDefId, attributes ) to PCM user.
+    And   PCM user share the attributes from requested credentials to OCM verifer.
+    And   OCM verifer verify the presentation acknowledgement.    
+    Then  Presentation request should be in 'verified' state.
+
+Scenario: OCM admin verify credentials
+    Given PCM user should hold credentials in there wallet.
+    When  OCM admin send a credential request to PCM user.
+    And   PCM user decline the credential request witch will requested from OCM admin.   

features/proof/sendPresentationRequest.feature

+As a OCM Admin 
+    I want to verify credentials.
+
+Scenario: OCM admin verify credentials
+    Given PCM user should hold credentials in there wallet.
+    And   PCM user connection must be in trusted state with verifer.
+    When  OCM verifer orgnization sends a proof presentation request with following fields ( connectionId, schemaId or credentialDefId, attributes ) to PCM user.
+    And   PCM user share the attributes from requested credentials to OCM verifer.
+    And   OCM verifer verify the presentation acknowledgement.    
+    Then  Presentation request should be in 'verified' state.
+
+Scenario: PCM user decline proof request
+    Given PCM user should hold credentials in there wallet.
+    And   PCM user connection must be in trusted state with verifer.
+    When  OCM verifer orgnization sends a proof presentation request with following fields ( connectionId, schemaId or credentialDefId, attributes ) to PCM user.
+    And   PCM user declines the presentation request.
+    Then  Presentation request is not 'verified'.  
+

features/proof/sendPrincipalCredentialPresentationRequest.feature

+Feature: I am able to prove as GAIA-X ecosystem member.
+         To make the existing connection trusted.
+
+Scenario: Make the existing connection trusted
+    Given PCM user should hold principal membership credentials in there wallet.
+    And   PCM user connection must be in complete state with verifer.
+    When  OCM verifer orgnization sends a proof presentation request with following fields ( schemaId, attributes ) to PCM user.
+    And   PCM user share the attributes from requested credentials to OCM verifer.
+    And   OCM verifer verify the presentation acknowledgement.    
+    Then  Presentation request should be in 'trusted' state.