|
+5.10 Assertion Validation |
5.10 Assertion ValidationThe RP SHALL validate the signature on all signed attribute bundles in the assertion using the verification key from the CSP that issued the signed attribute bundle. The RP SHALL validate the signature of the assertion using the verification key of the subscriber-controlled wallet contained in the signed attribute bundle. The RP SHALL validate the assertion by checking that all the following are true: Bundle verification: Ensure that the bundle was issued to the wallet that is presenting the assertion to the RP.
Issuer verification: If a specific wallet was requested by the RP, ensure that the assertion was issued by the requested wallet.
Time validation: Ensure that the validity time window is within acceptable limits of the current timestamp.
Audience restriction: Ensure that this RP is the intended recipient of the assertion.
Nonce: Ensure that the cryptographic nonce included in the RP’s request is also included in the presentation.
Transaction terms: Ensure that the IAL, AAL, and FAL represented by the assertion are allowable under the applicable trust agreement and are suitable for the RP’s needs.
Assertion identifier: Ensure that the assertion has not been replayed within its validity time window at this RP by validating a transaction specific assertion identifier, such as a wallet-provided nonce.
Additionally, if a mechanism for invalidating attribute bundles is provided by the CSP, the RP SHOULD use this mechanism to determine whether the attribute bundle has been invalidated by the CSP since its issuance, as discussed in Sec. 5.1.1. This validation mechanism is particularly suited for attribute bundles with long or indeterminate lifetimes, since proactive invalidation by the CSP could occur long before expiration of the attribute bundle. 1. Übersicht
1.1 Referenzen1.2 Identifizierte Anforderungen1.3 Zugehörige Regulierungen2. Identifizierte Anforderungen
3. Zugehörige Regulierungen
|