Struct AccessConnectorTokenHandler 

pub(crate) struct AccessConnectorTokenHandler {
    inner: Arc<RwLock<Inner>>,
}

Token handler for the PAM access connector.

Fields

inner: Arc<RwLock<Inner>>

Implementations

impl AccessConnectorTokenHandler

pub(crate) fn key_store(&self) -> Option<KeyStore<KeySlotIds>>

The key store core created. Clones of a [KeyStore] share their keys, so clearing it on revocation reaches core too.

pub(crate) fn set_session(&self, session: Arc<SessionManager>)

Requests made before this lands cannot be authenticated.

pub(crate) fn session(&self) -> Option<Arc<SessionManager>>

Trait Implementations

impl Clone for AccessConnectorTokenHandler

fn clone(&self) -> AccessConnectorTokenHandler

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Default for AccessConnectorTokenHandler

fn default() -> AccessConnectorTokenHandler

Returns the “default value” for a type.

impl TokenHandler for AccessConnectorTokenHandler

fn set_tokens<'life0, 'async_trait>( &'life0 self, _token: String, _refresh_token: Option<String>, _expires_in: u64, ) -> Pin<Box<dyn Future<Output = ()> + Send + 'async_trait>>

where Self: 'async_trait, 'life0: 'async_trait,

No-op: SessionManager owns the bearer and its renewal.

fn initialize_middleware( &self, _state_registry: &StateRegistry, _identity_config: Configuration, key_store: KeyStore<KeySlotIds>, ) -> 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_sm_login_method<'life0, 'async_trait>( &'life0 self, _login_method: ServiceAccountLoginMethod, ) -> Pin<Box<dyn Future<Output = ()> + Send + 'async_trait>>

where 'life0: 'async_trait, Self: 'async_trait,

Secrets-Manager-only hook for storing the Service Account login method on the handler itself. SM tokens are not persisted, so the login method lives in-memory on the SecretsManagerTokenHandler implementation. The default no-op implementation is intentional: handlers that do not back Secrets Manager (PM, Noop, ClientManaged) should ignore this call. This will be removed once the auth crate fully owns the login process.