Expand description
How credentials go on a request. Fizzy takes a bearer token (Authorization: Bearer)
for API access tokens, or a session cookie (Cookie: session_token=) for a session
signed in through a magic link. There is no OAuth and no refresh: a 401 is final.
Structs§
- Bearer
Auth Authorization: Bearer <token>, for API access tokens.- Cookie
Auth Cookie: session_token=<token>, for a session signed in through a magic link.- NoAuth
- No credentials at all, for the calls that come before there are any: creating a session and redeeming its magic link.
- Static
Token Provider - A fixed token, from an environment variable say. It prints as
[REDACTED], so a{:?}of the provider — or of anything holding one — cannot put the token in a log.
Constants§
- SESSION_
COOKIE - The cookie a signed-in session is carried in.
Traits§
- Auth
Strategy - Puts credentials on a request.
BearerAuthandCookieAuthare the two Fizzy takes; anything else can plug in here. - Token
Provider - Supplies the token each request goes out with.