Deploy to GitHub pages

c_nonce-jwt_proof/en/_sources/pid-eaa-issuance.rst.txt

@@ -308,7 +308,7 @@ The ``client_assertion`` is signed using the private key that is created during
 
 **Steps 16-17 (DPoP Proof for Credential Endpoint):** The Wallet Instance for requesting the Digital Credential creates a proof of possession with ``c_nonce`` obtained in **Step 15** and using the private key used for the DPoP, signing a DPoP Proof JWT according to (:rfc:`9449`) Section 4. The ``jwk`` value in the ``proof`` parameter MUST be equal to the public key referenced in the DPoP.
 
-**Step 18 (Credential Request):** The Wallet Instance requests the Digital Credential to the PID/(Q)EAA Credential endpoint. The request MUST contain the *Access Token*, the *DPoP Proof JWT*, the *credential type*, the `proof` (proof of possession of the key), and the ``format`` parameters, where the *proof* is an object containing the proof of possession of the cryptographic key material the issued PID/(Q)EAA Digital Credential would be bound to. The PID/(Q)EAA Provider performs the following checks on the Credential endpoint to verify the *proof*:
+**Step 18 (Credential Request):** The Wallet Instance sends a request for the Digital Credential to the PID/(Q)EAA Credential endpoint. This request MUST include the Access Token, DPoP Proof JWT, credential type, proof (which demonstrates possession of the key), and format parameters. The proof parameter MUST be an object that contains evidence of possession of the cryptographic key material to which the issued PID/(Q)EAA Digital Credential will be bound. To verify the proof, the PID/(Q)EAA Provider conducts the following checks at the Credential endpoint:
 
   1. all required claims for the *JWT proof* type are included as defined in the table of Section :ref:`Token Request <sec_token_request>`; 
   2. the key proof is explicitly typed using header parameters as defined for that *proof* type; 

c_nonce-jwt_proof/en/pid-eaa-issuance.html

@@ -1342,7 +1342,7 @@ <h2>Detailed Flow<a class="headerlink" href="#detailed-flow" title="Permalink to
 </pre></div>
 </div>
 <p><strong>Steps 16-17 (DPoP Proof for Credential Endpoint):</strong> The Wallet Instance for requesting the Digital Credential creates a proof of possession with <code class="docutils literal notranslate"><span class="pre">c_nonce</span></code> obtained in <strong>Step 15</strong> and using the private key used for the DPoP, signing a DPoP Proof JWT according to (<span class="target" id="index-29"></span><a class="rfc reference external" href="https://datatracker.ietf.org/doc/html/rfc9449.html"><strong>RFC 9449</strong></a>) Section 4. The <code class="docutils literal notranslate"><span class="pre">jwk</span></code> value in the <code class="docutils literal notranslate"><span class="pre">proof</span></code> parameter MUST be equal to the public key referenced in the DPoP.</p>
-<p><strong>Step 18 (Credential Request):</strong> The Wallet Instance requests the Digital Credential to the PID/(Q)EAA Credential endpoint. The request MUST contain the <em>Access Token</em>, the <em>DPoP Proof JWT</em>, the <em>credential type</em>, the <cite>proof</cite> (proof of possession of the key), and the <code class="docutils literal notranslate"><span class="pre">format</span></code> parameters, where the <em>proof</em> is an object containing the proof of possession of the cryptographic key material the issued PID/(Q)EAA Digital Credential would be bound to. The PID/(Q)EAA Provider performs the following checks on the Credential endpoint to verify the <em>proof</em>:</p>
+<p><strong>Step 18 (Credential Request):</strong> The Wallet Instance sends a request for the Digital Credential to the PID/(Q)EAA Credential endpoint. This request MUST include the Access Token, DPoP Proof JWT, credential type, proof (which demonstrates possession of the key), and format parameters. The proof parameter MUST be an object that contains evidence of possession of the cryptographic key material to which the issued PID/(Q)EAA Digital Credential will be bound. To verify the proof, the PID/(Q)EAA Provider conducts the following checks at the Credential endpoint:</p>
 <blockquote>
 <div><ol class="arabic simple">
 <li><p>all required claims for the <em>JWT proof</em> type are included as defined in the table of Section <a class="reference internal" href="#sec-token-request"><span class="std std-ref">Token Request</span></a>;</p></li>