Issuance of transaction_ids

The following points are not clearly defined in the spec right now:

(A) In a batch (deferred) issuance, will there be one transaction_id for all deferred credentials or will it be the same for all?

(B) How is the transaction_id or are the transaction_ids returned? There is the following example in the spec:

HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store

{
   "credential_responses":[
      {
         "transaction_id":"8xLOxBtZp8"
      },
      {
         "format":"jwt_vc_json",
         "credential":"YXNkZnNhZGZkamZqZGFza23....29tZTIzMjMyMzIzMjMy"
      }
   ],
   "c_nonce":"fGFF7UkhLa",
   "c_nonce_expires_in":86400
}

This shows one transaction_id per credential; in case there are many deferred credentials, will it be the same for all credentials (repeated, say, 100 times for 100 credentials) or will there be different ones?

(C) How is the wallet supposed to hit the deferred credential endpoint and what will be returned from the endpoint? See also https://bitbucket.org/openid/connect/issues/1759/no-need-for-credential-endpoint-when-we

Comments (1)