Skip to content

Specify SHA-256 as the JWK Thumbprint hashing algorithm. - #266

Merged
drubery merged 1 commit into
w3c:mainfrom
sbovet-g:main
Aug 27, 2026
Merged

drubery merged 1 commit into
w3c:mainfrom
sbovet-g:main

Conversation

@sbovet-g

Copy link
Copy Markdown
Contributor

This change doesn't add agility, meaning SHA-256 remains the only option.

The upcoming DBSC SSO effort might replace this part of the spec, so let's not spend too much time adding algo agility here.

This change doesn't add agility, meaning SHA-256 remains the only option.

The upcoming [DBSC SSO](https://github.com/WICG/dbsc-sso) effort might replace this part of the spec, so let's not spend too much time adding algo agility here.
@drubery

drubery commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

Ah, yeah. I hadn't noticed that RFC7638 abstracts over choice of hash. SHA-256 was the intent.

@drubery
drubery merged commit 3794efa into w3c:main Aug 27, 2026
2 checks passed
github-actions Bot added a commit that referenced this pull request Aug 27, 2026
SHA: 3794efa
Reason: push, by drubery

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

2 participants