Skip to content

708 better guidance how the verifier matches the incoming direct post request with the user session #734

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
paulbastian wants to merge 4 commits into
base: main
Choose a base branch
from
Open

708 better guidance how the verifier matches the incoming direct post request with the user session #734

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
07a892f
Clarify `state` parameter requirements in 1.0
paulbastian Apr 27, 2026
45f62ac
Update 'state' requirement and clarify usage
paulbastian Apr 27, 2026
b12729f
Apply suggestions from code review
paulbastian Apr 27, 2026
3d704ac
Apply suggestions from code review
paulbastian Apr 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions 1.0/openid-4-verifiable-presentations-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -367,7 +367,7 @@ The following additional considerations are given for pre-existing Authorization
: REQUIRED. Defined in [@!RFC6749]. This specification defines additional requirements to enable the use of Client Identifier Prefixes as described in (#client_metadata_management). The Client Identifier can be created by parties other than the Wallet and it is considered unique within the context of the Wallet when used in combination with the Client Identifier Prefix.

`state`:
: REQUIRED under the conditions defined in (#nkb-credentials). Otherwise, `state` is OPTIONAL. `state` values MUST only contain ASCII URL safe characters (uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde).
: REQUIRED under the conditions defined in (#nkb-credentials). Otherwise, `state` is RECOMMENDED, see (#security_considerations_direct_post). `state` values MUST only contain ASCII URL safe characters (uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde).

## Requesting Presentations without Holder Binding Proofs {#nkb-credentials}

Expand Down Expand Up @@ -3566,9 +3566,10 @@ The technology described in this specification was made available from contribut

-31

* Clarify that state is recommended to match text from Section 14.3.2. Protection of the Response URI
* Clarify that `encrypted_response_enc_values_supported` applies only if JWE content encryption algorithm is used
* Clarify that `aud` corresponds to `issuer` Wallet Metadata paremeter if Dynamic Discovery is used

-final

* https://openid.net/specs/openid-4-verifiable-presentations-1_0-final.html
* https://openid.net/specs/openid-4-verifiable-presentations-1_0-final.html
3 changes: 2 additions & 1 deletion 1.1/openid-4-verifiable-presentations-1_1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -363,7 +363,7 @@ The following additional considerations are given for pre-existing Authorization
: REQUIRED. Defined in [@!RFC6749]. This specification defines additional requirements to enable the use of Client Identifier Prefixes as described in (#client_metadata_management). The Client Identifier can be created by parties other than the Wallet and it is considered unique within the context of the Wallet when used in combination with the Client Identifier Prefix.

`state`:
: REQUIRED under the conditions defined in (#nkb-credentials). Otherwise, `state` is OPTIONAL. `state` values MUST only contain ASCII URL safe characters (uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde).
: REQUIRED under the conditions defined in (#nkb-credentials). Otherwise, `state` is RECOMMENDED, see (#security_considerations_direct_post). `state` values MUST only contain ASCII URL safe characters (uppercase and lowercase letters, decimal digits, hyphen, period, underscore, and tilde).

## Requesting Presentations without Holder Binding Proofs {#nkb-credentials}

Expand Down Expand Up @@ -3633,5 +3633,6 @@ The technology described in this specification was made available from contribut

* Add usage of HPKE for the `info` parameter.
* Add security consideration not to use VP Token as Access Token
* Clarify that state is recommended to match text from Section 14.3.2. Protection of the Response URI
* Clarify that `encrypted_response_enc_values_supported` applies only if JWE content encryption algorithm is used; e.g., it does not apply to JOSE HPKE
* Clarify that `aud` corresponds to `issuer` Wallet Metadata paremeter if Dynamic Discovery is used
Loading