4.1 release notes - #139
Open
javereec wants to merge 5 commits into
Open
Conversation
javereec
commented
Aug 10, 2026
| ## New Features | ||
|
|
||
| - SVX Verify sessions can now report the specific cryptographic key a presentation was bound to, making it easier for integrators to confirm proof of possession. | ||
| - **Transaction Data support** (per the [OpenID4VP](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html) specification): Verifiers can now attach additional context to a presentation request, and wallets can restrict which types of this data they are willing to accept. Verifiers can confirm that the credential presentation returned by a wallet was genuinely bound to the requested context, adding an extra layer of assurance to verification flows. |
Contributor
Author
Contributor
There was a problem hiding this comment.
@javereec added a short section called How to use Transaction Data
|
|
||
| - SVX Verify sessions can now report the specific cryptographic key a presentation was bound to, making it easier for integrators to confirm proof of possession. | ||
| - **Transaction Data support** (per the [OpenID4VP](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html) specification): Verifiers can now attach additional context to a presentation request, and wallets can restrict which types of this data they are willing to accept. Verifiers can confirm that the credential presentation returned by a wallet was genuinely bound to the requested context, adding an extra layer of assurance to verification flows. | ||
| - Certificate management now shows which signing key a managed certificate belongs to, and certificate listings support filtering and pagination. |
Contributor
Author
There was a problem hiding this comment.
@ragnika I think an example what would helpful in a separate section
| - **Transaction Data support** (per the [OpenID4VP](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html) specification): Verifiers can now attach additional context to a presentation request, and wallets can restrict which types of this data they are willing to accept. Verifiers can confirm that the credential presentation returned by a wallet was genuinely bound to the requested context, adding an extra layer of assurance to verification flows. | ||
| - Certificate management now shows which signing key a managed certificate belongs to, and certificate listings support filtering and pagination. | ||
| - Signing requests can now accept base64url-encoded input, in addition to plain text. | ||
| - Session data used by the authorization server can now be stored in Postgres as an alternative to Redis. |
| - Certificate management now shows which signing key a managed certificate belongs to, and certificate listings support filtering and pagination. | ||
| - Signing requests can now accept base64url-encoded input, in addition to plain text. | ||
| - Session data used by the authorization server can now be stored in Postgres as an alternative to Redis. | ||
| - OAuth clients can now be marked as native or web applications, enabling correct authentication behavior for native app integrations. |
| ## Improvements | ||
|
|
||
| - Failed SVX Verify presentations now include a more detailed reason, making it easier to understand why a verification did not succeed. | ||
| - The demo issuance and verification pages have moved into the main dashboard; the previous standalone demo pages have been retired. |
Contributor
Author
There was a problem hiding this comment.
@Matthew-Meeco can you add a section with screenshots of the pages
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.