Skip to content

Commit

Permalink
fix: removed batch language updates
Browse files Browse the repository at this point in the history
  • Loading branch information
awoie committed Aug 6, 2024
1 parent 7c31153 commit 938d019
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions openid-4-verifiable-credential-issuance-1_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -1042,9 +1042,9 @@ Cache-Control: no-store

### Credential Issuer Provided Nonce {#issuer-provided-nonce}

The Credential Issuer that requires the Client to send a key proof of possession of the key material for the Credential to be bound to (`proof` or `proofs`) MAY receive a Credential Request or Batch Credential Request without a or with an invalid server-provided `c_nonce` value included in the `proof` or `proofs` parameter. In such a case, the Credential Issuer MAY provide the Client with a `c_nonce` defined in (#credential-response) in a Credential Error Response or Batch Credential Error Response using `invalid_proof` error code defined in (#credential-error-response).
The Credential Issuer that requires the Client to send a key proof of possession of the key material for the Credential to be bound to (`proof` or `proofs`) MAY receive a Credential Request without a or with an invalid server-provided `c_nonce` value included in the `proof` or `proofs` parameter. In such a case, the Credential Issuer MAY provide the Client with a `c_nonce` defined in (#credential-response) in a Credential Error Response using `invalid_proof` error code defined in (#credential-error-response).

If the Client has not received a `c_nonce` and the Credential Issuer Metadata contains `proof_types_supported` indicating a key proof is required for the requested Credential, the Client MUST send a Credential Request or Batch Credential Request that contains a `proof` or `proofs` parameter that is fully valid but does not include a server-provided `c_nonce` value. It is the Credential Issuer policy whether or not a `c_nonce` value is required in the key proofs.
If the Client has not received a `c_nonce` and the Credential Issuer Metadata contains `proof_types_supported` indicating a key proof is required for the requested Credential, the Client MUST send a Credential Request that contains a `proof` or `proofs` parameter that is fully valid but does not include a server-provided `c_nonce` value. It is the Credential Issuer policy whether or not a `c_nonce` value is required in the key proofs.

If the Client received a `c_nonce`, the `c_nonce` value MUST be incorporated in the respective parameter in the `proof` or `proofs` object.

Expand Down

0 comments on commit 938d019

Please sign in to comment.