web-token (JWT Framework)

事实及其依据的检查

以下内容均非抄自文档。检查脚本 content/libraries/verify/web-token-jwt-framework/run.sh 于2026年10月20日在容器镜像 php:8.5.11-cli-trixie 中运行了 web-token (JWT Framework) 4.2.3；本页内容必须与它的输出一致，每条事实都列出了对应的输出行。

• JWS 算法

  HS256HS384HS512RS256RS384RS512PS256PS384PS512ES256ES384ES512EdDSA

  256/384/512 的 HS、RS、PS、ES 以及 EdDSA 的签名与验证均成功；没有 ES256K 或 Ed25519 算法类。

  检查记录

  fact jws-algorithms = HS256, HS384, HS512, RS256, RS384, RS512, PS256, PS384, PS512, ES256, ES384, ES512, EdDSA
  evidence jws-algorithms: ES256K: class Jose\Component\Signature\Algorithm\ES256K exists: false
  evidence jws-algorithms: Ed25519: class Jose\Component\Signature\Algorithm\Ed25519 exists: false

• ES256 签名编码

  raw

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

  检查记录

  fact jws-ecdsa-encoding = raw

• JWS 中的 DER 签名

  rejected

  DER 编码的 ES256 签名会让 verifyWithKey() 返回 false。

  检查记录

  fact jws-der-signature = rejected
  evidence jws-der-signature: false

• 算法允许列表

  required

  AlgorithmManager 就是允许列表：用只含 ES256 的管理器验证 RS256 令牌，报错 The algorithm "RS256" is not supported.

  检查记录

  fact jwt-algorithm-allowlist = required
  evidence jwt-algorithm-allowlist: RS256 token with an AlgorithmManager holding only ES256: InvalidArgumentException: The algorithm "RS256" is not supported.

• 未签名的令牌（alg none）

  opt-in

  除非把 None 算法类加入管理器，否则未签名的令牌会报错 The algorithm "none" is not supported.

  检查记录

  fact jwt-alg-none = opt-in
  evidence jwt-alg-none: with an ES256 AlgorithmManager: InvalidArgumentException: The algorithm "none" is not supported.; a None algorithm class exists: true

• 把公钥用作 HMAC 密钥

  rejected

  在同时允许 ES256 和 HS256 的情况下，以 PEM 文本为密钥的 HS256 令牌用 EC JWK 验证失败。

  检查记录

  fact jwt-hmac-public-key = rejected
  evidence jwt-hmac-public-key: AlgorithmManager [ES256, HS256] with the EC JWK: false

• 按 alg 检查曲线

  enforced

  用 P-384 密钥执行 ES256 签名成功了，但该库的验证器拒绝了生成的签名。

  检查记录

  fact jwt-ecdsa-curve-check = enforced
  evidence jwt-ecdsa-curve-check: ES256 with a P-384 key, signing: ok; verifying: false

• 解码时校验声明

  no

  对一小时前就已过期的令牌，JWSVerifier::verifyWithKey() 返回了 true；声明由单独的 ClaimCheckerManager 检查。

  检查记录

  fact jwt-claims-validated-on-decode = no
  evidence jwt-claims-validated-on-decode: JWSVerifier on a token expired an hour ago: ok

• 默认时钟偏差

  0s

  除非传入容差，否则 ExpirationTimeChecker 不容许任何时钟漂移：三秒前过期的令牌被拒绝。

  检查记录

  fact jwt-clock-skew = 0s

• 是否要求过期时间声明

  no

  必需声明中没有 exp 时，缺少它的令牌照样通过；把它列入必需声明后，抛出 MissingMandatoryClaimException。

  检查记录

  fact jwt-exp-required = no
  evidence jwt-exp-required: ExpirationTimeChecker without exp: ok; with exp listed as mandatory: Jose\Component\Checker\MissingMandatoryClaimException: The following claims are mandatory: exp.

用法

<?php
require 'vendor/autoload.php';

use Jose\Component\Checker\{ClaimCheckerManager, ExpirationTimeChecker, IssuerChecker};
use Jose\Component\Core\AlgorithmManager;
use Jose\Component\KeyManagement\JWKFactory;
use Jose\Component\Signature\Algorithm\ES256;
use Jose\Component\Signature\{JWSBuilder, JWSVerifier};
use Jose\Component\Signature\Serializer\CompactSerializer;

$jwk = JWKFactory::createECKey('P-256');
$algorithms = new AlgorithmManager([new ES256()]); // the allow-list
$payload = json_encode(['sub' => 'user-42', 'iss' => 'https://auth.example.com', 'exp' => time() + 600]);
$jws = (new JWSBuilder($algorithms))->create()->withPayload($payload)->addSignature($jwk, ['alg' => 'ES256'])->build();
$token = (new CompactSerializer())->serialize($jws, 0);

// The signature check does not look at claims: run the claim checkers as a second step.
$parsed = (new CompactSerializer())->unserialize($token);
$valid = (new JWSVerifier($algorithms))->verifyWithKey($parsed, $jwk->toPublic(), 0);
$clock = new class implements Psr\Clock\ClockInterface { public function now(): DateTimeImmutable { return new DateTimeImmutable(); } };
$claims = json_decode($parsed->getPayload(), true);
(new ClaimCheckerManager([new ExpirationTimeChecker($clock, 30), new IssuerChecker(['https://auth.example.com'])]))->check($claims, ['exp', 'iss']);
echo 'valid: ', var_export($valid, true), ', sub: ', $claims['sub'], "\n";