Clarification of simplified verification flow required

The current openid-4-verifiable-presentations-1_0.md specification says that the RP can send an authorization request to the wallet’s authorisation endpoint to request only a vp_token. An example request is given

GET /authorize?
    response_type=vp_token
    &client_id=https%3A%2F%2Fclient.example.org%2Fcb
    &redirect_uri=https%3A%2F%2Fclient.example.org%2Fcb
    &presentation_definition=...
    &nonce=n-0S6_WzA2Mj HTTP/1.1

However no corresponding simplified result is given. In particular, is it correct to assume that no access_token needs to be returned with the vp_token? So is the following the simplest result one could expect?

{
"vp_token": "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6ImRpZDpleGFtcGxlOjB4YWJjI2tleTEifQ.eV05xQXhmdDdFVDZsa0gtNFM2VXgzclNHQW1jek1vaEVFZjhlQ2VOLWpDOFdla2RQbDZ6S1pRa.ft_Eq4IniBrr7gtzRfrYj8Vy1aPXuFZU - 6_ ai0wvaKcsrzI4JkQEKTvbJwdvIeuGuTqy7ipO",
"presentation_submission": {
"id": "Selective disclosure example presentation",
"definition_id": "Selective disclosure example",
"descriptor_map": [{
"id": "ID Card with constraints",
"format": "jwt_vp",
"path": "$",
"path_nested": {
"format": "jwt_vc",
"path": "$.verifiableCredential[0]"
}
}]
}
}

If so, can we add such an example?

One final point. Could we please include the JSON examples inline in the .md file rather than as references to examples in the examples directory as this makes it far more difficult to see if the examples are correct. (You have to find the right directory inside the examples directory and then the right file in the right directory).

Comments (7)