verify
Verifies the integrity of the returned documents, according to ISO/IEC 18013-5.
The following checks are performed for each MdocDocument instance in documents:
For MdocDocument.issuerAuth the signature is checked against the leaf certificate in the associated X.509 chain.
The document type in the MSO matches the docType in the response.
The MSO's signed date is within the validity period of the leaf certificate in the associated X.509 chain.
If rejectIfValidUntilAfterNotAfter is true, the MSO's validUntil date does not exceed the leaf certificate's validity period.
The MSO is validity period includes the passed-in atTime.
The data returned in MdocDocument.issuerNamespaces is checked against digests in the MSO.
The device-authentication structures (ECDSA or MAC) are checked.
If any data elements are returned as part of DeviceSigned, all those data elements or their namespace are included in the keyAuthorizations map in the DeviceKeyInfo map in the MSO.
For each transaction data in the list, verifies that transaction hash is present in the response and matches the hash of the source transaction data
The following checks are performed for each OtherDocument instance in otherDocuments:
For document format
dc+sd-jwt:The SD-JWT+KB is constructed from decompressing OtherDocument.data
Verification is done with org.multipaz.sdjwt.SdJwtKb.verify using the issuer signing key from the leaf certificate in the org.multipaz.sdjwt.SdJwt.x5c, both
nonceandaudderived frombase64url(SHA-256(SessionTranscriptBytes))per ISO/IEC 18013-5 Second Edition Annex H.2, and creation-time checked against the passed-in atTime.The credential's validity period includes the passed-in atTime.
The following checks are expected to be done by the application:
Determining whether the issuer's document signing certificate is trusted. An application can use org.multipaz.trustmanagement.TrustManagerInterface to do this.
Checking whether any X.509 certificates in the issuer chain are revoked (e.g. via CRL or OCSP) and whether the MSO itself is revoked (e.g. via org.multipaz.revocation.RevocationChecker against org.multipaz.mdoc.mso.MobileSecurityObject.revocationStatus). Neither check is performed automatically by this method.
Checking the integrity of any Zero-Knowledge Proofs for documents returned in zkDocuments. An application can use org.multipaz.mdoc.zkp.ZkSystem to do this.
Checking or decrypting any encrypted documents returned in encryptedDocuments. Use EncryptedDocuments.decrypt to do this.
Parameters
the session transcript to use.
the ephemeral reader key or null if not using session encryption.
the request to which this response is given; required when matching returned documents against request constraints or when transaction data was sent in the request.
repository that contains all known transaction types; must be given if deviceRequest is given and contains transaction data.
the point in time for validating whether returned documents are valid.
if true, rejects the MSO if its validUntil date exceeds the Document Signer certificate validity period according to ISO/IEC 18013-5 Second Edition clause 12.8.1. This defaults to false as this check is discretionary for readers ("may reject") and official test vectors in ISO/IEC 18013-5:2021 Annex D have validUntil after notAfter.
Throws
if validation fails.