1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
//! Token management (owned by 16-02): `TokenManager`, single-flight refresh
//! guard, and local JWKS verification.
// §21.7.2 DPoP proof verification (contract 1.16). Gated on `rest`/`actix`:
// the ten checks need `sha2`, `base64` and `subtle`, which those features
// bring in. A `--no-default-features` consumer keeps `verify_token_binding`
// (pure claim comparison) and has no proof verifier — which per §10.1 rule 9
// means it must refuse `jkt`-bound tokens, not accept them as bearer tokens.
pub use Claims;
// §10.1 rule 9 (contract 1.15). Ungated alongside `Claims`, because
// `Claims::verify_certificate_binding` is pure claim logic a
// `--no-default-features` consumer must be able to apply.
pub use CnfClaim;
// §10.1 rule 9 extended for DPoP (contract 1.16). Ungated for the same reason
// as `CnfClaim`: `Claims::verify_token_binding` is pure claim comparison, and
// a `--no-default-features` consumer must be able to apply the full rule and
// not just its certificate half.
pub use PresentedProofs;
pub use certificate_thumbprint_s256;
pub use ;
pub use TokenManager;
// §21.7.2 (contract 1.16). `verify_dpop_proof` returns the proof key's
// thumbprint, which is exactly what `Claims::verify_token_binding` expects as
// `dpop_thumbprint` — the two are meant to be used together, and the
// thumbprint can only ever originate from a proof that verified.
pub use ;