Generalized Verification API in Veramo Core

As an Integrator of Veramo I would like to be able to use a single generalized Verification API that automatically verifies a various set of input data according to a given policy input.

Acceptance Criteria:

• There should be a single Verification API within Veramo core (Proposal: agent.verify({ payload: {...}, policy: {...} }))
• The fist step of the verification API is the identification of the payload format and determines what dynamic module is able to verify the given Payload.
• The generalized verification API allows for the registration of Modules to support new payloads.
• In the initial Implementation VC-JWT and VC-JSON-LD Credentials are supported with respective VC-JWT and VC-JSON-LD Verification Modules.
• Furthermore it should be able to Verify Verifiable Presentation Representations of JWT / JSON-LD Credentials
• The Verification API and the Verification Modules take an optional policy file that is able to influence the verification outcome.
• Each VC Verification Module is implemented independently, but generally it needs to verify the following. a) Schema / Data format. It needs to verify that the given payload matches the referenced Schema or Context b) Signature Verification. Verify that a Issuer Signature matches the given Credential and Issuer. c) Credential Status: Verify that the Credential Status of the VC is still valid:
• Policy files can model the following: a) Override certain assumption: Policy may allow to accept revoked credentials or self-signed Signatures. b) Tighten Validation conditions: Further restrict conditions of credential verification (e.g. similar to passing a PE), e.g. where certain values are expected. (Credential issued by specific issuer A) c) Trust Frameworks d) … TBD
• Fixed Error Types for Verification Errors a) b) c) d)
• Policy Design, Module Integration and Payload Identification will be design as part of this ticket.

[italobb]

I would like to reinforce the importance of this issue hoping it can be prioritized. The usage of the DIF “well-known DID configuration” spec with the purpose of implementing discoverability and interoperability requires such support from Veramo.

[awoie]

@rado0x54 pls add tasks for this epic.