Struct AuthManager 

pub struct AuthManager { /* private fields */ }

Selects exactly one active auth strategy per deployment, chosen via the auth_method config value — there is no runtime engine for resolving multiple simultaneously-required schemes. These three methods (SqlServer/Windows/AzureAd) are the complete set SQL Server’s TDS protocol accepts (see core::config_schema::AuthMethod’s doc comment) — there is no per-request/HTTP-header credential relay concept here: this server always connects to SQL Server with the one set of operator-configured credentials resolved via credentials()’s config/ env/keychain cascade below, regardless of how a caller reaches this MCP server (stdio or HTTP).

Implementations

impl AuthManager

pub fn new(auth_method: AuthMethod) -> Self

pub async fn login(&mut self, config: &AuthConfig) -> Result<Credentials>

pub fn set_credentials(&mut self, credentials: Credentials)

Seeds in-memory credentials directly, bypassing OS-keychain/file storage entirely — for tests (which must never touch the real OS keychain as a side effect of running) and for callers that already hold validated credentials from elsewhere.

pub async fn credentials(&mut self) -> Result<Credentials>

pub async fn resolve_tds_auth(&mut self) -> Result<AuthMethod>

Resolves this deployment’s active tiberius::AuthMethod from the config/env/keychain cascade (credentials()).