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
//! `frontend-oidc` mode — config, runtime, service, capabilities, and
//! cross-boundary contracts.
//!
//! In a `frontend-oidc` deployment the browser handles the full OIDC
//! authorization code flow (via `oauth4webapi` or similar). The Rust backend
//! does not run the OIDC redirect/callback/token-exchange flow itself.
//!
//! # Module structure
//!
//! - [`contracts`] — config projection and claims-check script types
//! - [`capabilities`] / [`FrontendOidcModeCapabilities`] /
//! [`UnsafeFrontendClientSecret`] — opt-in unsafe features
//! - [`config`] / [`FrontendOidcModeConfig`] /
//! [`ResolvedFrontendOidcModeConfig`] / [`FrontendOidcModeConfigSource`] —
//! config
//! - [`runtime`] / [`FrontendOidcModeRuntime`] — runtime (projection helpers)
//! - [`service`] / [`FrontendOidcModeService`] — route-facing service
//!
//! # Substrate integration
//!
//! Token verification and propagation are substrate concerns owned by
//! [`access_token_substrate`](crate::access_token_substrate). This mode
//! provides the contracts that describe how frontend-produced tokens are
//! consumed by the substrate, but does not own the verification or
//! propagation logic itself.
// --- Public re-exports: capabilities ---
pub use ;
// --- Public re-exports: config ---
pub use ;
// --- Public re-exports: contracts ---
pub use ;
// --- Public re-exports: runtime ---
pub use FrontendOidcModeRuntime;
// --- Public re-exports: service ---
pub use FrontendOidcModeService;