public interface IAccountAuthorityTurns a credential into an account handle. The one thing the engine does not ship.
Remarks
⚠ There is no credential store in this repository and there is not going to be one. A game engine that shipped one would ship a liability its authors do not operate: hashing parameters that age, breach response, password reset, multi-factor, account recovery, and a regulatory surface that differs per market. Every one of those is a product decision.
What the gate actually needs is much smaller — which account is this request for — and every deployment already has something that answers it: an OIDC provider, Steam, EOS, a console platform SDK, or the studio's existing account service. This interface is that answer's shape, and Vixen.Live.Persistence maps the handle it returns onto the account the world knows.
Same position doc 16 took on Steam and EOS transports and doc 27 M-Q1 restated: the engine ships the seam and one honest development implementation, not the integration.
Fields and properties (1)
string SchemeWhich Scheme this one answers for.
Methods (1)
Task<AuthorityResult> AuthenticateAsync(string credential, CancellationToken cancellation)Decides who a credential belongs to.
Used by (2)
- DevelopmentAuthorityVixen.Live.Gate
- GateServiceVixen.Live.Gate