One ES256 migration, three ways to mangle a valid signature
We moved JWT signing from RS256 to ES256 and every token we minted was cryptographically valid — and rejected. Three times, for three different reasons: DER where JWS wants raw R‖S, integer padding that fails one token in 128, and a base64 dialect that changed under our feet. Here's how to read the mangled bytes and name the guilty layer from the signature length alone.


