Skip to content

Clarify how hashing works in transaction_data_hashes#621

Merged
Sakurann merged 2 commits intomainfrom
transaction-data-hashing-clarification
Jun 3, 2025
Merged

Clarify how hashing works in transaction_data_hashes#621
Sakurann merged 2 commits intomainfrom
transaction-data-hashing-clarification

Conversation

@jogu
Copy link
Collaborator

@jogu jogu commented May 30, 2025

Make it clear that the hash is base64url encoded, and that the data hashed is the string that was in the request (without base64url decoding it first).

closes #457
closes #615

tlenz pushed a commit to a-sit-plus/vck that referenced this pull request Jun 2, 2025
…shes

Reason: there was a discussion in openID4VP about how transaction_data_hashes
        have to be calculated. Agreement to use text from v23,
        see openid/OpenID4VP#621
@jogu jogu added this to the Final 1.0 milestone Jun 3, 2025
tlenz pushed a commit to a-sit-plus/vck that referenced this pull request Jun 3, 2025
…shes

Reason: there was a discussion in openID4VP about how transaction_data_hashes
        have to be calculated. Agreement to use text from v23,
        see openid/OpenID4VP#621 .
@c2bo
Copy link
Member

c2bo commented Jun 3, 2025

Also closes #615

tlenz pushed a commit to a-sit-plus/vck that referenced this pull request Jun 3, 2025
…shes

Reason: there was a discussion in openID4VP about how transaction_data_hashes
        have to be calculated. Agreement to use text from v23,
        see openid/OpenID4VP#621
@Sakurann Sakurann requested a review from tplooker June 3, 2025 18:01
@Sakurann
Copy link
Collaborator

Sakurann commented Jun 3, 2025

@ubamrein

@Sakurann Sakurann merged commit 0bdcd77 into main Jun 3, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify transaction_data_hashes input and output encoding in SD-JWT

4 participants