You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update signature tests for the protected-header "alg" requirement (web-token#651)
Following the algorithm-confusion fix (GHSA-jc38-x7x8-2xc8), JWSVerifier
reads "alg" only from the integrity-protected header and rejects a JWS
whose "alg" is absent from it. Three existing tests asserted the previous
behaviour where "alg" could come from the unprotected header (RFC 7520
§4.7 / §4.8 examples); they now assert that such tokens are rejected, and
the expected exception message is updated accordingly.
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
$this->expectExceptionMessage('No "alg" parameter set in the header.');
933
+
$this->expectExceptionMessage('No "alg" parameter set in the protected header.');
934
934
935
935
$payload = "It\xe2\x80\x99s a dangerous business, Frodo, going out your door. You step onto the road, and if you don't keep your feet, there\xe2\x80\x99s no knowing where you might be swept off to.";
0 commit comments