Struct distant_net::AuthServer

pub struct AuthServer<ChallengeFn, VerifyFn, InfoFn, ErrorFn> where
    ChallengeFn: Fn(Vec<AuthQuestion>, HashMap<String, String>) -> Vec<String> + Send + Sync,
    VerifyFn: Fn(AuthVerifyKind, String) -> bool + Send + Sync,
    InfoFn: Fn(String) + Send + Sync,
    ErrorFn: Fn(AuthErrorKind, String) + Send + Sync, {
    pub on_challenge: ChallengeFn,
    pub on_verify: VerifyFn,
    pub on_info: InfoFn,
    pub on_error: ErrorFn,
}

Server that handles authentication

Fields

on_challenge: ChallengeFn

on_verify: VerifyFn

on_info: InfoFn

on_error: ErrorFn

Trait Implementations

impl<ChallengeFn, VerifyFn, InfoFn, ErrorFn> Server for AuthServer<ChallengeFn, VerifyFn, InfoFn, ErrorFn> where
    ChallengeFn: Fn(Vec<AuthQuestion>, HashMap<String, String>) -> Vec<String> + Send + Sync,
    VerifyFn: Fn(AuthVerifyKind, String) -> bool + Send + Sync,
    InfoFn: Fn(String) + Send + Sync,
    ErrorFn: Fn(AuthErrorKind, String) + Send + Sync, 

type Request = Auth

Type of data received by the server

type Response = Auth

Type of data sent back by the server

type LocalData = RwLock<Option<XChaCha20Poly1305Codec>>

Type of data to store locally tied to the specific connection

fn on_request<'life0, 'async_trait>(
    &'life0 self,
    ctx: ServerCtx<Self::Request, Self::Response, Self::LocalData>
) -> Pin<Box<dyn Future<Output = ()> + Send + 'async_trait>> where
    'life0: 'async_trait,
    Self: 'async_trait, 

Invoked upon receiving a request from a client. The server should process this request, which can be found in ctx, and send one or more replies in response.

fn config(&self) -> ServerConfig

Returns configuration tied to server instance

fn on_accept<'life0, 'life1, 'async_trait>(
    &'life0 self,
    local_data: &'life1 mut Self::LocalData
) -> Pin<Box<dyn Future<Output = ()> + Send + 'async_trait>> where
    'life0: 'async_trait,
    'life1: 'async_trait,
    Self: Sync + 'async_trait, 

Invoked immediately on server start, being provided the raw listener to use (untyped transport), and returning the listener when ready to start (enabling servers that need to tweak a listener to do so) Invoked upon a new connection becoming established, which provides a mutable reference to the data created for the connection. This can be useful in performing some additional initialization on the data prior to it being used anywhere else.