fix: Relying Party - discovery_uri, removal of DPoP and random fragme…

…nt for request and response endpoints - seq diag
italia · Dec 12, 2023 · c7b9f1b · c7b9f1b
1 parent d2fda63
commit c7b9f1b
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/en/relying-party-solution.rst b/docs/en/relying-party-solution.rst
@@ -57,7 +57,7 @@ Below a sequence diagram that summarizes the interactions between all the involv
 
 .. image:: ../../images/cross_device_auth_seq_diagram.svg
   :align: center
-  :target: https://www.plantuml.com/plantuml/svg/XLLDRoCt3BthLn3keKwGfDdjpK2ApRhf9hjjFRMzoIL086jeMuqiJVKnZblqlvSQUcnFFhf04C0It-Dx5Cdv4ABqCQsCa2awcrOpz4A8InMTXzxNWBu7Ca0IOkQU-E3x03zZhHM67dptgruiuqUJK5J4evMkf8tGkvF6O8GRI_HMOSEnxeOaeZgL2xIHCqY1jWJAqWqRezbeku223ZTDP8r293ZzYI03kCCPJD1dEM1bhHSoQcT5aZcWnW6CyQ-48KBXNKGLiQIJu99Nn79n0TaGNAQuH4iv6p3q2u-1VlElOYa37i75XP0gwbf6p0fgR1CCFT9Pm-6y_fj1RTPxspy-3iI4nyVaBP73w61l7PHpZvheNn9wfdX8NeDl9TVO6lzZF7GbmcWCrzDfGGbBxSaVz7yyVty4QnsNe8oc50-wFEcGIH9Hwg1SZNwJJqI9XzR4tkXQY8LtgI9DBhJF3iwQpRR2QG2JfLi3rQzLL96n_3vqknx0g4BRt3xh291LTGB6AMb0Tielri3GYPAMI26pxWwldg8dUVTsP-xU7fYxjnrtV3JtRiKAcImtcc36NEzYD9csygQebbPdKKDPoPasEceC45t6Ttc1M2gdRHHlD0RMqYGw3Hdx_maQ51jiEsSq-nDLVF4qRHqkOynHdUc0gKyXxa9kqUlvvbd8RnXbAQFSHqcZoqp_-MuA4xsmCYQFBwvRNLZ2RT4FHnoGzdhdpeDoDi_DlXvftmX3P-VQhx0yj9Iwh_1YY4AL6McAkA7hwY6wHxHl5FngM_1SRtQlvSmWTCQP2LhGtk1hJSfLPk0PgU2VXv65TxKkqPD27I0lBd3p9k0NfEC6INVIbg_o4yQw21vhKbMU7SZQfXfweh5HImCt8IJq_CPC-TRRxLb8diB03QXsL49uoegGMvd2Q8dVVBgUVXfVNVqkNaSC10oNg1xXsXco1Lzm0n-rBQcl6Y648jlqLxWG24wk2N8AAL14mrMbcT4A7Wd8Qr1JNVBDeSNeeEQcRLwmuCSw4mAcIxJjxEz6qRY09SWOlPwbY640HCawzHoer1J9UrHx2inj3z8Zo5fgGvtHB8Ac5EAWPb-hjXtuux3r0trUrP2Q-_88zaFRhE0VtfszW_Vdvp3wGZB-wNdUoCrQwWrW6MCL87d3hUotlVsWyixyzt0eri-7dbVmHAwmiu5v0YKf3YptC6EszgtbNUFkC_9vCk3AFLl6469MqSy6suy86zX-kBW8hEFoDUX2rsWPqf1al-444iKP0_XKDM_ZF8IaSkVDascqVw1_QMN-0m00
+  :target: https://www.plantuml.com/plantuml/uml/VLLTKnit57tNhpZZFXIOG4dwvXaw8PG6ahQus0alp33oxhMj8ajRVQnnE_tllHUn_d1DNZopqZr7vzoFw_SnwP3ot2gTatTvFgQWb3glaW_eVOaKUj0HMQcnVoe7tqVyJAsfAFRmtQzcEaiVR2RLC8-fJADTGkzEMqi9ruxfNKN2WSLsI6QgOpqbbyeBMf6hmQziXzsINHetnO0FbnA9bfJAEFw98NtSqHX32Y87JhTcgfFnJcKj0ItrSKj_POe9W-0JLObgFea-XufPpiuWXd2UqumSl_aCni4WKEJlyZMOwKY7E3jJkagcrOb4GKlT0nU1v4pZw2WoX8wEq6gRwTwDVMP7oMDj5PNtZsOFF1IP3paOX2AG6R0mQGQDe5tjvvW4FPqp2yCx_t_SNlYQS7EBgz5emDvg4zWc3duyVNTOu9KrZ7amzPkjLvWIjOcLRoaivKJLjEbGhVqkb9e6dniMwsDNVNXdbo-9pdqCPtu1JcEdg66_KYQ-NVHnqv23tEuq1dJJl87rbRRGMrLG2nJeiDAEII6igyFBfnHOthrRcRjt6-RktQuxFfe4FoyA2vdqcnB6KeZ1pN3KoHjHDND6H5teHe-DDSbGHFA2t-O5ipJUkAHUwG-IRk3JADXlFy2eah1rszwC_wGgxPPcbOVpb2HgQqWm2ZccLSXN2cQot0dvZPAkTTBhA6rDBVIVxaOOcgdJAGVwttMdYsfy7Hp4mnAGrtedFg3oJiPddO-yReGBxoOcpAdUj9HtgY3pw8FvkmmWpsiZZEZceMqUadyazqh2BryIBlakxeqUMyBML1U23hGskAz9IvOBy8HLbC_Do47mhQafi48J8ViBVY81-8Nu-1d9TzhLU_aPutn2e9PLrISRiifJiYHg6GrjSHrZfb1gN2XVgzsQXULL54i3LYigfOBpZ99MvZ3UvTSVhqOVRoylVrVx4Ns5YnbLZxZobctXCotnmRXQ-ag4CCfFnFd0nyXmTisGO-Ge4SBLvB4r5HuPMBQZaRpmpQR5v5cED6sfuA0KwqGfZ6RakjbVZQBraMheb88PvqIn3wOiEiq4d6gEB0lM10wKjeSE1DrgOwKpP158AaXjvEnBqxL3-OzuyOE3ii6HvPxgGsmChQpW7zwUlCMxqrFSV6OP__J2oqQMNT7hOvPI4v63BQqSNdhxePAT-U_cK2nsXxwiuA6UqzO6BXEeMN4iSZTV56lVNDx5RRUqFmtx9NCxonZI_OG3CTZzYHG39Hk79Gb5n_a-wDIqv0f4I21-unjaZhCMzDH8RU03OgwayoRPFcj_ppzvRly3
 
 The details of each step shown in the previous picture are described in the table below.
 
@@ -70,9 +70,9 @@ The details of each step shown in the previous picture are described in the tabl
     - **Description**
   * - **1**, **2**
     - The User requests to access to a protected resource, the Relying Party redirects the User to a discovery page in which the User selects the *Login with the Wallet* button. The Authorization flow starts.
-  * - **3**, **4**, **5**
+  * - **3**, **4**,
     - The Relying Party provides to the Wallet Instance the where a generic signed Authorization Request Object is available for download and the ``discovery_uri``  where the Wallet Instance can provide its technical capabilities to the Relying Party. 
-  * - **6**, **7**, **8**, **9**
+  * - **5**, **6**, **7**, **8**, **9**
     - In the **Cross Device Flow**: the Request URI is provided in the form of a QR Code that is shown to the User. The User frames the QRCode with the Wallet Instance and extracts  ``client_id``, ``request_uri`` and ``discovery_uri``. In the **Same Device Flow** the Relying Party provide the same information of the Cross-Device flow but in the form of HTTP Redirect Location (302). 
   * - **10**
     - The Wallet Instance provides its metadata to the Relying Party, informing it about some features and limitations of its implementations.