Nimbus JOSE + JWT

事实及其依据的检查

以下内容均非抄自文档。检查脚本 content/libraries/verify/nimbus-jose-jwt/run.sh 于2026年10月20日在容器镜像 maven:3.9.16-eclipse-temurin-25 中运行了 Nimbus JOSE + JWT 10.10；本页内容必须与它的输出一致，每条事实都列出了对应的输出行。

• JWS 算法

  HS256HS384HS512RS256RS384RS512PS256PS384PS512ES256ES384ES512EdDSAEd25519

  在 JDK 上，256/384/512 的 HS、RS、PS 和 ES 以及 EdDSA 和 Ed25519 的签名与验证均成功；使用 JDK 自带的提供程序时，ES256K 和 Ed448 未能完成往返测试。

  检查记录

  fact jws-algorithms = HS256, HS384, HS512, RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, ES512, EdDSA, Ed25519
  evidence jws-algorithms: ES256K: not round-tripped with the JDK providers
  evidence jws-algorithms: Ed448: not round-tripped with the JDK providers

• ES256 签名编码

  raw

  ES256 签名是 64 字节的原始 r‖s。

  检查记录

  fact jws-ecdsa-encoding = raw

• JWS 中的 DER 签名

  rejected

  带有 DER 编码 ES256 签名的令牌验证失败。

  检查记录

  fact jws-der-signature = rejected
  evidence jws-der-signature: not verified

• 算法允许列表

  required

  DefaultJWTProcessor 需要密钥选择器：没有选择器时报错 No JWS key selector is configured；针对 ES256 的选择器拒绝了 RS256 令牌。

  检查记录

  fact jwt-algorithm-allowlist = required
  evidence jwt-algorithm-allowlist: DefaultJWTProcessor with a JWSVerificationKeySelector for ES256, RS256 token: BadJOSEException: Signed JWT rejected: Another algorithm expected, or no matching key(s) found
  evidence jwt-algorithm-allowlist: DefaultJWTProcessor without a key selector: BadJOSEException: Signed JWT rejected: No JWS key selector is configured

• 未签名的令牌（alg none）

  rejected

  处理器会拒绝未签名的令牌，报错 Unsecured (plain) JWTs are rejected, extend class to handle。

  检查记录

  fact jwt-alg-none = rejected
  evidence jwt-alg-none: DefaultJWTProcessor: BadJOSEException: Unsecured (plain) JWTs are rejected, extend class to handle
  evidence jwt-alg-none: SignedJWT.parse: ParseException: Invalid JWS header: Not a JWS header

• 把公钥用作 HMAC 密钥

  rejected

  以 PEM 文本为密钥的 HS256 令牌被配置为 ES256 的处理器拒绝，但用该 PEM 文本手动构建的 MACVerifier 让它验证通过了。

  检查记录

  fact jwt-hmac-public-key = rejected
  evidence jwt-hmac-public-key: DefaultJWTProcessor with the ES256 key selector: BadJOSEException: Signed JWT rejected: Another algorithm expected, or no matching key(s) found
  evidence jwt-hmac-public-key: a MACVerifier built from the PEM text by hand: verified

• 按 alg 检查曲线

  enforced

  用 P-384 密钥签名 ES256 时报错 The ES256 algorithm is not allowed or supported by the JWS signer: Supported algorithms: [ES384]。

  检查记录

  fact jwt-ecdsa-curve-check = enforced
  evidence jwt-ecdsa-curve-check: JOSEException: The ES256 algorithm is not allowed or supported by the JWS signer: Supported algorithms: [ES384]

• 默认时钟偏差

  60s

  DefaultJWTClaimsVerifier 允许 60 秒的偏差（DEFAULT_MAX_CLOCK_SKEW_SECONDS）。

  检查记录

  fact jwt-clock-skew = 60s
  evidence jwt-clock-skew: DefaultJWTClaimsVerifier.DEFAULT_MAX_CLOCK_SKEW_SECONDS = 60

• 是否要求过期时间声明

  no

  不含 exp 的令牌通过了默认的声明验证器；把 exp 列为必需声明后，它会报错 JWT missing required claims: [exp]。

  检查记录

  fact jwt-exp-required = no
  evidence jwt-exp-required: with DefaultJWTClaimsVerifier requiring exp: BadJWTException: JWT missing required claims: [exp]

• 不依赖 Google Tink 的 Ed25519

  fails

  classpath 中没有 Google Tink 时，用 Ed25519Signer 签名报错 NoClassDefFoundError: com/google/crypto/tink/subtle/Ed25519Sign$KeyPair。

  检查记录

  fact ed25519-without-tink = fails
  evidence ed25519-without-tink: NoClassDefFoundError: com/google/crypto/tink/subtle/Ed25519Sign$KeyPair

用法

import com.nimbusds.jose.*;
import com.nimbusds.jose.crypto.ECDSASigner;
import com.nimbusds.jose.jwk.*;
import com.nimbusds.jose.jwk.gen.ECKeyGenerator;
import com.nimbusds.jose.jwk.source.ImmutableJWKSet;
import com.nimbusds.jose.proc.*;
import com.nimbusds.jwt.*;
import com.nimbusds.jwt.proc.*;
import java.util.*;

public class Usage {
    public static void main(String[] args) throws Exception {
        ECKey key = new ECKeyGenerator(Curve.P_256).keyID("2026-10").generate();
        JWTClaimsSet claims = new JWTClaimsSet.Builder().subject("user-42").issuer("https://auth.example.com")
            .expirationTime(new Date(System.currentTimeMillis() + 600_000)).build();
        SignedJWT jwt = new SignedJWT(new JWSHeader.Builder(JWSAlgorithm.ES256).keyID(key.getKeyID()).build(), claims);
        jwt.sign(new ECDSASigner(key));

        // The key selector is the algorithm allow-list; the claims verifier requires iss and exp.
        DefaultJWTProcessor<SecurityContext> processor = new DefaultJWTProcessor<>();
        processor.setJWSKeySelector(new JWSVerificationKeySelector<>(JWSAlgorithm.ES256, new ImmutableJWKSet<>(new JWKSet(key.toPublicJWK()))));
        processor.setJWTClaimsSetVerifier(new DefaultJWTClaimsVerifier<>(
            new JWTClaimsSet.Builder().issuer("https://auth.example.com").build(), new HashSet<>(List.of("sub", "exp"))));
        System.out.println("sub: " + processor.process(jwt.serialize(), null).getSubject());
    }
}