from Aggelos
two cases
the unencrypted which is this
POST https://example-verifier.com/callback
Content-Type: application/x-www-form-urlencoded
vp_token=eyJhbGciOiJFUzI1NiIsImtpZCI6InIzZ2Q4ZXBoIn0.eyJpc3MiOiJodHRwczovL2FwcC53YWxsZXQuY29tIiwic3ViIjoidXNlcklkIiwidnBfaGFzaCI6InNka2oiLCJ2aF9jbGFpbXMiOnsic29tZUF0dHIiOiJ2YWx1ZSJ9fQ.GdIoVKojlS...
&presentation_submission=%7B%22id%22%3A%22123abc%22%2C%22definition_id%22%3A%22def123%22%2C%22descriptor_map%22%3A%5B%7B%22id%22%3A%22driver_license%22%2C%22path%22%3A%22%24%22%7D%5D%7D
&state=4ad3b177
(the values are placeholders not examples)
the vp token is the sdjwt
the presentation_submission is something like this
{
"id": "123abc",
"definition_id": "def123",
"descriptor_map": [{
"id": "driver_license",
"path": "$"
}]
}
10:03
the state is from the verifier's request
10:03
(presentation submission is url encoded)
10:05
and the second case is the encrypted version in which vp token presentation submission and state is all put into one jwe string and being put in a filed "response"
10:07
the second case is chosen when the response_Mode is DIRECT_POST_JWT and the verifier has indicated it wants an encrypted response by providing authorization_encrypted_response_alg and a public key in S.client_metadata.jwks
from Aggelos
two cases
the unencrypted which is this
POST https://example-verifier.com/callback
Content-Type: application/x-www-form-urlencoded
vp_token=eyJhbGciOiJFUzI1NiIsImtpZCI6InIzZ2Q4ZXBoIn0.eyJpc3MiOiJodHRwczovL2FwcC53YWxsZXQuY29tIiwic3ViIjoidXNlcklkIiwidnBfaGFzaCI6InNka2oiLCJ2aF9jbGFpbXMiOnsic29tZUF0dHIiOiJ2YWx1ZSJ9fQ.GdIoVKojlS...
&presentation_submission=%7B%22id%22%3A%22123abc%22%2C%22definition_id%22%3A%22def123%22%2C%22descriptor_map%22%3A%5B%7B%22id%22%3A%22driver_license%22%2C%22path%22%3A%22%24%22%7D%5D%7D
&state=4ad3b177
(the values are placeholders not examples)
the vp token is the sdjwt
the presentation_submission is something like this
{
"id": "123abc",
"definition_id": "def123",
"descriptor_map": [{
"id": "driver_license",
"path": "$"
}]
}
10:03
the state is from the verifier's request
10:03
(presentation submission is url encoded)
10:05
and the second case is the encrypted version in which vp token presentation submission and state is all put into one jwe string and being put in a filed "response"
10:07
the second case is chosen when the response_Mode is DIRECT_POST_JWT and the verifier has indicated it wants an encrypted response by providing authorization_encrypted_response_alg and a public key in S.client_metadata.jwks