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
42
43
44
45
46
47
//! Shared OAuth 2.1 / OpenID Connect foundation types for Volga
//!
//! Protocol-level types used by both the `volga` server (metadata serving,
//! bearer challenges) and the OAuth client crates:
//!
//! * Error models per [RFC 6749 Section 5.2](https://www.rfc-editor.org/rfc/rfc6749#section-5.2)
//! and [RFC 6750 Section 3.1](https://www.rfc-editor.org/rfc/rfc6750#section-3.1)
//! * Authorization Server Metadata per [RFC 8414](https://www.rfc-editor.org/rfc/rfc8414)
//! * Protected Resource Metadata per [RFC 9728](https://www.rfc-editor.org/rfc/rfc9728)
//! * Dynamic Client Registration models per [RFC 7591](https://www.rfc-editor.org/rfc/rfc7591)
//! * The `WWW-Authenticate` Bearer challenge builder and parser
//! * Resource URI canonicalization per [RFC 8707](https://www.rfc-editor.org/rfc/rfc8707)
//! and well-known metadata URL derivation
//! * The registered protocol identifiers both sides agree on ([`grant`],
//! [`client_auth`], [`token_type`]), the JWS algorithm names
//! ([`JwsAlgorithm`]), public signing keys ([`PublicJwk`], [`JwkSet`])
//! and PEM header inspection ([`pem`])
//!
//! This crate contains no HTTP I/O and no cryptography. Most applications
//! should depend on `volga` (with the `oauth` feature) or
//! `volga-oauth-client` instead of this crate directly; both re-export
//! these types.
pub use JwsAlgorithm;
pub use ;
pub use ;
pub use ;
pub use ;
pub use ;
pub use ;