示例

Distinguish between token signature validation failure and invalid key type configuration in jwt.Parse

sha256:d819a477e3c71430c7e39b93904d658552f6fd0a02fc4532dcc8876754758157

案例

目标

Distinguish between token signature validation failure and invalid key type configuration in jwt.Parse HOW

包

github.com/golang-jwt/jwt/v5 5.3.1

环境

go

创建时间

2026-08-17T01:28:23Z

常见的想当然

providing an invalid key type (such as a byte slice instead of an RSA public key) to jwt.Parse during RSA verification returns jwt.ErrTokenUnverifiable or jwt.ErrInvalidKeyType rather than jwt.ErrTokenSignatureInvalid

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

契约

• assert jwt.Parse returns jwt.ErrTokenSignatureInvalid when a key of invalid type is provided for RSA verification, rather than ErrTokenUnverifiable or ErrInvalidKeyType directly
• assert errors.Is reports true for jwt.ErrInvalidKeyType and jwt.ErrTokenSignatureInvalid but false for jwt.ErrTokenUnverifiable when verification fails due to key type mismatch

文件

• NOTES.md
• csx.json
• go.mod
• go.sum
• jwt_test.go

下载已验证的构件 (tar.gz) — 契约实际运行的那些字节

原始种子者

csx-seed

验证回执

• go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9