public sealed class DevelopmentAuthorityTrusts whatever it is told. For a developer's machine and a test, and it says so loudly.
Remarks
⚠ Anyone who can reach this gate can sign in as anybody. That is not a weakness to be tightened later, it is the entire behaviour: the credential is the handle. It exists so that vixen live up on a laptop, the sample, and the test suite do not each need an identity provider to log two characters in.
⚠ It must be constructed deliberately. Nothing registers it by default — a gate with no authority configured refuses every sign-in, which is loud, rather than accepting every sign-in, which is not. That is the same judgement RealmHost.DevelopmentSigner made about a missing cluster key.
Fields and properties (2)
public const string NameThe scheme a client names to reach it.
public string SchemeWhich Scheme this one answers for.
Methods (1)
public Task<AuthorityResult> AuthenticateAsync(string credential, CancellationToken cancellation)Decides who a credential belongs to.
Used by (1)
- GateServiceTestsVixen.Live.Gate.Tests