Deploy to GitHub pages

versione-corrente/en/_sources/wallet-attestation.rst.txt

@@ -104,6 +104,7 @@ Wallet Instance Initialization and Registration
     **Device Integrity Service:** In this section the Device Integrity Service is considered as it is provided by device manufacturers. This service allows the verification of a key being securely stored within the device's hardware through a signed object. Additionally, it offers the verifiable proof that a specific Wallet Instance is authentic, unaltered, and in its original state using a specialized signed document made for this scope.
 
     The service also incorporates details in the signed object, such as the device type, model, app version, operating system version, bootloader status, and other relevant information to assess the device has not been compromised. For Android the service used is `Key Attestation`_ in addition to `Play Integrity API`_, while for iOS the `DeviceCheck`_ service.
+    This service, specifically developed by the manufacturer, is already integrated within the Android or iOS SDKs, so there is no need for a predefined endpoint to access it. Moreover, as it is specifically developed in the mobile architecture, it does not need to be registered as a Federation Entity, through the national accreditation systems.
 
 **Step 8**: The Device Integrity Service performs the following actions:
 
@@ -476,22 +477,22 @@ The body of the Wallet Attestation JWT MUST contain:
       - :rfc:`7800`
     * - **aal**
       - JSON String asserting the authentication level of the Wallet and the key as asserted in the cnf claim.
-      - 
+      -
     * - **authorization_endpoint**
       - URL of the Wallet Authorization Endpoint (Universal Link).
-      - 
+      -
     * - **response_types_supported**
       - JSON array containing a list of the OAuth 2.0 ``response_type`` values.
-      - 
+      -
     * - **response_modes_supported**
       - JSON array containing a list of the OAuth 2.0 "response_mode" values that this authorization server supports.
       - :rfc:`8414`
     * - **vp_formats_supported**
       - JSON object with name/value pairs, identifying a Credential format supported by the Wallet.
-      - 
+      -
     * - **request_object_signing_alg_values_supported**
       - JSON array containing a list of the JWS signing algorithms (alg values) supported.
-      - 
+      -
     * - **presentation_definition_uri_supported**
       - Boolean value specifying whether the Wallet Instance supports the transfer of presentation_definition by reference. MUST be set to false.
       -

versione-corrente/en/wallet-attestation.html

@@ -1162,7 +1162,8 @@ <h3>Wallet Instance Initialization and Registration<a class="headerlink" href="#
 <div class="admonition note">
 <p class="admonition-title">Note</p>
 <p><strong>Device Integrity Service:</strong> In this section the Device Integrity Service is considered as it is provided by device manufacturers. This service allows the verification of a key being securely stored within the device's hardware through a signed object. Additionally, it offers the verifiable proof that a specific Wallet Instance is authentic, unaltered, and in its original state using a specialized signed document made for this scope.</p>
-<p>The service also incorporates details in the signed object, such as the device type, model, app version, operating system version, bootloader status, and other relevant information to assess the device has not been compromised. For Android the service used is <a class="reference external" href="https://developer.android.com/privacy-and-security/security-key-attestation">Key Attestation</a> in addition to <a class="reference external" href="https://developer.android.com/google/play/integrity?hl=it">Play Integrity API</a>, while for iOS the <a class="reference external" href="https://developer.apple.com/documentation/devicecheck">DeviceCheck</a> service.</p>
+<p>The service also incorporates details in the signed object, such as the device type, model, app version, operating system version, bootloader status, and other relevant information to assess the device has not been compromised. For Android the service used is <a class="reference external" href="https://developer.android.com/privacy-and-security/security-key-attestation">Key Attestation</a> in addition to <a class="reference external" href="https://developer.android.com/google/play/integrity?hl=it">Play Integrity API</a>, while for iOS the <a class="reference external" href="https://developer.apple.com/documentation/devicecheck">DeviceCheck</a> service.
+This service, specifically developed by the manufacturer, is already integrated within the Android or iOS SDKs, so there is no need for a predefined endpoint to access it. Moreover, as it is specifically developed in the mobile architecture, it does not need to be registered as a Federation Entity, through the national accreditation systems.</p>
 </div>
 <p><strong>Step 8</strong>: The Device Integrity Service performs the following actions:</p>
 <ul class="simple">