Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
g3-auth
Session auth for Dioxus fullstack apps on SurrealDB, part of the g3 stack: sessions stored in the database, the signed-in user on every request, and a guard that denies by default.
Setup
[]
= "0.1"
[]
= ["dioxus/server", "g3-auth/server"]
Only server pulls in the server side (axum, axum_session, SurrealDB).
Without it, #[public] and PublicRoutes still compile, so the same code
builds for web and mobile.
Usage
Stay signed in on a phone
A native app's HTTP client forgets cookies when the process dies, so without
this every relaunch signs everyone out. Enable the feature for the platform and
call init first in main (it does nothing on the web and the server):
[]
= ["dioxus/mobile", "g3-auth/mobile"] # or "g3-auth/desktop"
Sign in with Google
= { = "0.1", = ["google"] }
[]
= ["dioxus/server", "g3-auth/server"]
Put the button where it goes; it is Google's own button on the web and a system account picker on Android:
GoogleSignIn
On the server, say how a Google identity becomes one of your accounts and merge the callback before the session layers:
;
router
.merge
.layer
The web client id is public and read from GOOGLE_OAUTH_CLIENT_ID at build
time by the client and at run time by the server. Android also needs an
Android OAuth client for the app's package and signing key in the same Google
Cloud project, or the system flow returns no token.
The callback checks Google's g_csrf_token (cookie against form field) for you,
so a page cannot sign a visitor in with a token of its own.
Sign in with Apple
= { = "0.1", = ["google", "apple"] }
AppleSignIn // the button; Apple's redirect on the web, the system sheet on iOS
;
router
.merge
.layer
Load g3_auth::APPLE_SCHEMA beside SESSIONS_SCHEMA. APPLE_SERVICES_ID is
the web Services ID, read at build time by the client and at run time by the
server; APP_ORIGIN is the public origin Apple returns to. Add a Sign in with
Apple key (APPLE_TEAM_ID, APPLE_KEY_ID, APPLE_PRIVATE_KEY or
APPLE_PRIVATE_KEY_PATH) and the server exchanges the authorization code with
Apple, which also gives you a refresh token. Call apple::revoke_token with it
when the account is deleted. Apple needs HTTPS and refuses localhost, so try
the web flow through a tunnel. The apple module docs list how each sign-in is
checked.
Rate limits
Enable it in the app's server feature, not on the dependency, because it implies
g3-auth's server and a client build with that on pulls SurrealDB in:
[]
= ["g3-auth/server", "g3-auth/rate-limit"]
let limits = new
.client_ip_header_from_env // e.g. cf-connecting-ip, when only Cloudflare can reach the app
.limit
.limit;
let router = limits.apply;
A session-keyed limit only slows a browser: an attacker drops the cookie for a fresh bucket. Key the sign-in and sign-up endpoints on the address.
The guard
Every request needs a signed-in user unless it is for a static asset, or a
page or server function marked #[public]:
/// The splash asks this before it knows whether anyone is signed in.
pub async
Pages are marked on the route enum, next to #[route]:
Forgetting #[public] is the safe mistake: a signed-out caller gets a 401
JSON body the client can decode, and a signed-out page load is redirected
to the splash. Opening an endpoint up is one reviewable line next to the
function or page, not an edit to a list somewhere else.
g3_auth::public_endpoints() and Route::PUBLIC_PATTERNS list them all, for
pinning in a test.
Setup, innermost layer first:
use ;
// table `user`, name field `display_name`
pub type SessionContext = SessionContext;
// Panics at startup if the splash isn't `#[public]`: the redirect would loop.
let guard = for_routes;
router
.layer
.layer
.layer
.layer
Sessions live in SurrealDB through SurrealSessionPool; load
g3_auth::SESSIONS_SCHEMA for its table. Mark the session cookie Secure in
production: SessionConfig::default().with_secure(!cfg!(debug_assertions)).
The derive matches request paths against the marked routes' own patterns and
never parses a path into the enum: a catch-all
#[redirect("/:..segments", ..)] parses every path, including every /api/
one, as its target, so "parses as the splash" would open the whole app. For
the same reason it refuses #[public] on a top-level catch-all route.
A server function called during server-side rendering runs without any
middleware, so the guard covers HTTP requests only. Functions acting on
"the current user" should still check session_user.anonymous.
License
Licensed under either of Apache License, Version 2.0 or MIT license at your option.