pub trait Identity:
Send
+ Sync
+ Debug {
// Required methods
fn verify(&self, claim: &str) -> Result<Actor, Rejected>;
fn kind(&self) -> &'static str;
// Provided methods
fn verifies(&self) -> bool { ... }
fn login(&self) -> Option<&RelyingParty> { ... }
}Expand description
How a claimed identity becomes a verified one.
Required Methods§
Provided Methods§
Sourcefn verifies(&self) -> bool
fn verifies(&self) -> bool
Whether this provider verifies anything at all.
Exists so the runtime can say it is unauthenticated rather than leaving it to be
inferred. docs/42 §42.6’s whole point is that an absent control was invisible.
Sourcefn login(&self) -> Option<&RelyingParty>
fn login(&self) -> Option<&RelyingParty>
The browser-facing half, for a provider that can run a login flow.
None for both of this module’s providers, and that is the honest answer rather than a
missing feature: neither issues anything, so neither has anywhere to send a browser.
crate::oidc::RelyingParty does, and the HTTP edge asks this rather than being told which
provider is configured.