Credential verification
Document Rails provides two options for credential verification - an implementation of the OpenID for Verifiable Presentations protocol and a separate verification API which supports pluggable transport mechanisms.
Usage
Both options are useful in different scenarios, depending on how the presentation is acquired in the first place.
OID4VP
-
Support scenarios where Document Rails handles the entire communication with the wallet, and where your application serves as a relay.
-
Supported by third-party wallets and is highly interoperable with different holder solutions.
-
Automatically maps verification results to credentials and credential variables stored within your organization, removing the need to manually parse the verification result.
Verification API
-
Provides comparatively low-level primitives for validating credentials, allowing you to implement your own credential exchange protocols and manually communicate with the credential holder.
-
API is generalized to handle popular credential kinds using the same infrastructure.
-
Returns unmapped verification results, allowing you to inspect the verified credentials without losing any detail