Class AccountVerificationPolicy
- Namespace
- FishMMO.Server.Implementation
- Assembly
- FishMMO.Server.dll
Single source of truth for the development-only "skip email verification" policy
driven by the AutoVerifyAccounts configuration key.
Two call sites must agree on this answer:
- Account creation, which persists
verified = trueinstead of generating a verify code, queueing a verification email, and enrolling mandatory TOTP. - The login lookup, which otherwise rejects an unverified account once
verification_email_sent_athas been stamped. Without the login side honouring the flag, accounts created before auto-verify was enabled (or created against a production build) stay locked out of a local server forever.
The compile-time guard is deliberate: a production player build ignores the key
entirely, so a Development LoginServer.cfg that leaks into a production
deployment cannot re-enable the bypass. Consequently the flag also has no effect in a
server binary built with the Production working environment — build the server with
the Development working environment for local testing.
public static class AccountVerificationPolicy
- Inheritance
-
AccountVerificationPolicy
- Inherited Members
Fields
AutoVerifyAccountsKey
Configuration key that enables the development email-verification bypass.
public const string AutoVerifyAccountsKey = "AutoVerifyAccounts"
Field Value
Methods
IsAutoVerifyEnabled(IServerConfiguration)
Returns true when new accounts should be verified on creation and unverified
accounts should be allowed to log in. Always false outside the editor and
development builds.
public static bool IsAutoVerifyEnabled(IServerConfiguration configuration)
Parameters
configurationIServerConfigurationServer configuration; a null configuration fails closed.