Struct NoopTokenHandler 

pub struct NoopTokenHandler;

A token handler that does not attach any tokens. Useful for testing or for Clients that do not require authentication.

Trait Implementations

impl Clone for NoopTokenHandler

fn clone(&self) -> NoopTokenHandler

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Middleware for NoopTokenHandler

fn handle<'life0, 'life1, 'life2, 'async_trait>( &'life0 self, req: Request, ext: &'life1 mut Extensions, next: Next<'life2>, ) -> Pin<Box<dyn Future<Output = Result<Response, Error>> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait, 'life1: 'async_trait, 'life2: 'async_trait,

Invoked with a request before sending it. If you want to continue processing the request, you should explicitly call next.run(req, extensions).

impl TokenHandler for NoopTokenHandler

fn initialize_middleware( &self, _login_method: Arc<RwLock<Option<Arc<LoginMethod>>>>, _identity_config: Configuration, _key_store: KeyStore<KeyIds>, ) -> Arc<dyn Middleware>

Initialize middleware that handles token attachment and renewal. This middleware should look for the presence of the [bitwarden_api_base::AuthRequired] extension to decide when to attach tokens. It’s then free to attach tokens as it sees fit, including pausing and retrying requests to renew tokens.

fn set_tokens( &self, _token: String, _refresh_token: Option<String>, _expires_on: u64, )

This method is available only as a backwards compatibility measure until all the auth-related code is moved out of core. Once that is done, setting tokens should be always done either during renewal (as part of the middleware) or during registration/login, in which case it would be up to the auth crate to internally set those tokens when initializing the client.

impl Copy for NoopTokenHandler