Struct AuthStrategyFn 

pub struct AuthStrategyFn<F> { /* private fields */ }

AuthStrategy backed by a user-supplied async closure that returns a ServiceToken.

Example

use stack_auth::{AuthError, AuthStrategyFn, SecretToken, ServiceToken};

let strategy = AuthStrategyFn::new(|| async {
    // Real consumers would call into FFI / IPC / a cached token store.
    Ok::<_, AuthError>(ServiceToken::new(SecretToken::new("dummy.jwt.value".to_string())))
});

When to reach for this vs TokenStoreFn

• AuthStrategyFn: you control the entire token pipeline — fetch, refresh, cache. cipherstash-client calls your closure and uses whatever it returns, no further questions asked. Used by FFI bindings that proxy to a JS-side strategy doing all the work upstream.
• TokenStoreFn: you want stack-auth’s AccessKeyStrategy (or another concrete strategy) to do the HTTP/refresh work, and you just want to plug in custom persistence (a cookie, a KV blob, Redis).

Implementations

impl<F> AuthStrategyFn<F>

pub fn new(get_token: F) -> Self

Build an AuthStrategyFn from an async closure. The closure fires every time AuthStrategy::get_token is called on a reference to this strategy — typically once per cipherstash-client HTTP request, modulo any in-process caching the closure does internally.

Trait Implementations

impl<F, Fut> AuthStrategy for &AuthStrategyFn<F>

where F: Fn() -> Fut + Send + Sync, Fut: Future<Output = Result<ServiceToken, AuthError>> + Send,

Available on non-WebAssembly only.

fn get_token( self, ) -> impl Future<Output = Result<ServiceToken, AuthError>> + Send

Retrieve a valid access token, refreshing or re-authenticating as needed.