Package-level declarations
Types
Auth-decorated HTTP request: a (possibly rewritten) URL plus headers to attach.
Adds Authorization: Bearer <token> to every request. Used directly for Cesium Ion-style static-token endpoints. The Ion redirect dance (asset/<id>/endpoint -> tileset.json + signed-URL access token) is layered on top of this and wired in Phase 5.
Cesium Ion auth. Point the layer at https://api.cesium.com/v1/assets/<id>/endpoint; the first fetch returns {type, url, accessToken} — redirectFor follows url and captures the per-asset token for subsequent Bearer headers. One provider instance per asset.
Chains multiple providers so callers can stack auth (e.g. Ion bearer token + internal tracing headers). Providers are applied in order; each one sees the URL + headers produced by the previous one.
Attaches a fixed set of headers to every request. Useful for in-house tilesets that authenticate via a non-Bearer scheme (e.g. an internal X-API-Key header), and as a compositional building block under CompositeAuthProvider.
Google Photorealistic 3D Tiles auth. Static ?key=<apiKey> on every request; the ?session=<token> from the root response is propagated down the tree.
Passthrough auth provider for unauthenticated tilesets (self-hosted, public mirrors). Stateless singleton.
Round-trip serialization for TilesetAuthProvider credentials so a 3D-Tiles cache can carry enough info to be reopened from ContentManager.findEntry(...) without the caller having to supply credentials separately.
Plugged into every HTTP fetch a 3D Tiles layer makes: the root tileset.json, every external tileset reference, and every content payload. Providers can rewrite the URL (e.g. append a query parameter), append request headers, or both. They are also given the chance to mutate child URIs at parse time via rewriteChildUri so persistent state like Google's session token rides down the tree.