Expand description
Application identity policy at the endpoint’s actual admission boundary.
Structs§
- Prepared
User Creation - A creation candidate already normalized and admitted by the configured identity policy. Adapters persist its trusted mutations without normalizing it again, and retain their ordinary database hooks.
- User
Validation Context - The genuine logical endpoint call and its optional original HTTP request. Headerless server operations have an endpoint and no transport request.
- User
Validation Data - Mutable trusted candidate. Creation mutations are persisted; provider sign-in/link mutations affect only this validation copy.
- User
Validation Provider - Provider identity before application profile mapping.
- User
Validation Rejection - A policy denial. An empty error is an admission, and an empty description falls back to the error code, matching the callback’s public contract.
- User
Validation Source - Identity provenance supplied by the endpoint, never by its request body. The string method permits application-defined identity extensions.
Enums§
- User
Validation Action - The identity operation being admitted. Non-provider returning sign-ins do not invoke this policy because they do not introduce new identity data.
Traits§
Functions§
- validate_
user_ info - Apply configured validation against fresh provider identity at a returning sign-in or account-link boundary. Creation is owned by the store wrapper.