Expand description
Identity registration, federation-intake, and public resolution HTTP face.
Registration has two distinct routes with the same handle-only body: browser-session self service and bearer-authenticated operator manual registration. The route, never a client field, selects the authority path.
Federation intake is deliberately exposed only beside the authenticated
self-service route. Its did:web arm checks an exact, deployment-owned
HTTPS-origin allowlist before FederationIntake::intake can perform any
resolver network I/O.
Structs§
- DidWeb
Origin Allowlist - Exact HTTPS origins that may be resolved through the
did:webintake arm. - Federation
Intake Request - Federation-add payload.
- Identity
Registration Api - Rate-limited wire adapter over hosted mint, intake, and public local resolution.
- Register
Hosted Account Request - Handle-only registration payload.
- Register
Hosted Account Response - Browser registration result.
- Resolve
Identity Query - Public connect-time resolution query.
Traits§
- Federated
Identity Intake - Injectable federation-intake boundary.
- Hosted
Registration Mint - Injectable mint boundary used by the HTTP adapter and causal tests.
- Identity
Connect Time Resolver - Injectable connect-time boundary over authority-known local identities.
- Registration
Genesis Signer - Select and use the hybrid genesis signer for one authenticated request.