Request URI Method Post OIDC4VP vs IT Wallet

[stedcl]

Why into the OIDC4VP we found:

POST /request HTTP/1.1
Host: client.example.org
Content-Type: application/x-www-form-urlencoded
wallet_metadata=%7B%22vp_formats_supported%22%3A%7B%22jwt_vc_json%22%3A%7B%22alg_values_supported
%22%3A%5B%22ES256K%22%2C%22ES384%22%5D%7D%2C%22jwt_vp_json%22%3A%7B%22alg_values_supported%22%3A%5B%22ES256K%22%2C%22EdDSA%22%5D%7D%7D%7D&
wallet_nonce=qPmxiNFCR3QTm19POc8u

and into the IT Wallet spec we found:

POST /request-uri HTTP/1.1
HOST: relying-party.example.org
Content-Type: application/json

[peppelinux]

@stedcl here I read
https://github.com/italia/eudi-wallet-it-docs/blob/versione-corrente/docs/en/remote-flow.rst?plain=1#L104

the same here
https://italia.github.io/eudi-wallet-it-docs/versione-corrente/en/relying-party-solution.html

where did you find this misalignment?

[grausof]

This example is from OID4VP draft 22. The current specification are based on OID4Vp draft 20, we will align the specification in the next milestone.

[grausof]

Closed in favor of #473

[peppelinux]

We already have request uri method using post from 0.8.0

[stedcl]

The Content-Type is different