Merge pull request #554 from italia/iss-552

Authentic Source initiated flow

Author: peppelinux

docs/en/authentic-sources.rst

@@ -4,7 +4,7 @@
 Authentic Sources
 +++++++++++++++++++
 
-Authentic Sources are responsible for the authenticity of the User's attributes provided as Digital Credentials by Credential Issuers. During the Issuance Flow, Credential Issuers request from Authentic Sources the attributes required to provide the requested Credential. Authentic Sources MAY also provide a Credential Offer related to their Credential Issuers as defined in Section :ref:`Credential Offer Endpoint <Credential Offer Endpoint>`.
+Authentic Sources provide Users attributes to the Credential Issuers enabling them in the issuance of the Digital Credentials. During the Issuance Flow, Credential Issuers request from Authentic Sources the attributes required to provide the requested Credential. Authentic Sources MAY also provide a Credential Offer related to their Credential Issuers as defined in Section :ref:`Credential Offer Endpoint <Credential Offer Endpoint>`.
 
 Public Authentic Sources MUST interact with Credential Issuers via PDND according to the rules defined in Section :ref:`e-Service PDND <e-service-pdnd>` and in Section :ref:`Status Update by Authentic Sources <Status Update by Authentic Sources>`. See also Section :ref:`Authentic Source Catalogue <Authentic Source Catalogue>` for additional details.
 
@@ -17,4 +17,3 @@ Authentic Sources MUST:
 
     - cooperate with their Credential Issuers so that the attributes attested in a Digital Credential are always kept up to date. Public Authentic Sources MUST use PDND to notify their Credential Issuers of any update regarding attributes that have changed or are no longer valid. 
 
-

docs/en/pid-eaa-entity-configuration.rst

@@ -55,6 +55,8 @@ The *oauth_authorization_server* metadata MUST contain the following parameters.
     - JSON array containing a list of the supported *scope* values. See :rfc:`8414#section-2`.
   * - **response_modes_supported**
     - JSON array containing a list of the supported "response_mode" values, as specified in `OAuth 2.0 Multiple Response Type Encoding Practices <https://openid.net/specs/oauth-v2-multiple-response-types-1_0.html>`_. The supported values MAY be *query* and *form_post.jwt* (see `JARM`_).
+  * - **response_types_supported**
+    - JSON array containing a list of the supported "response_type" values, as specified in :rfc: `8414`. The supported value MUST be *code*.
   * - **authorization_signing_alg_values_supported**
     - JSON array containing a list of the :rfc:`7515` supported signing algorithms (*alg* values). The values MUST be set according to Section :ref:`Cryptographic algorithms`. See Section 4 of `JARM`_.
   * - **grant_types_supported**

examples/ec-eaa.json

@@ -52,6 +52,9 @@
                 "form_post.jwt",
                 "query"
             ],
+            "response_types_supported": [
+                "code"
+            ],
             "authorization_signing_alg_values_supported": [
                 "ES256",
                 "ES384",