Getting started with unified Flutter and Dart authentication
Move from installation to a working sign-in flow with a predictable setup sequence, shared provider contracts, and copyable starter code.
Plan the integration
The SDK is organized around one decision: your app should call the same login, refresh, and logout methods regardless of which identity provider sits behind the flow.
Recommended path
Install the core SDK, wire the redirect URI once, and add provider adapters only for the systems your product needs today.
What you get
Consistent session state, strongly typed auth methods, and provider pages that all follow the same operational model.
Install the SDK
The install step is intentionally small. Teams typically add the core package first, then layer in provider-specific adapters as they move beyond local prototyping.
- Use `flutter pub add` for application targets.
- Use `dart pub add` for backend utilities and command-line flows.
- Keep environment secrets outside source control from the first commit.
Initialize auth
Initialization sets the platform environment, client identity, redirect handling, and provider registry. After that, the same auth client can drive every sign-in path.
Deployment note
Keep client IDs, redirect URIs, and environment-specific issuers aligned across staging and production. Most login failures are configuration mismatches, not SDK failures.
Choose a provider integration
Every provider page follows the same structure so teams can compare setup, configuration, error handling, and code samples without re-learning the docs shape.
Integrate Firebase Authentication through the shared Aortem auth contract.
Connect Azure tenant policies and OpenID scopes with the same SDK surface.
Bridge Cognito user pools and hosted UI flows into a single SDK contract.
Deploy Auth0 login, MFA, and custom domains through consistent SDK primitives.
Map Okta org configuration, policies, and logout handling to Aortem auth APIs.
Support passwordless email and wallet logins using Aortem session management.
Use Stytch factors, OTP, and passkey flows through the same auth abstractions.
Bring Ping authorization servers and enterprise login policies into a single SDK flow.
Connect Transmit CIAM login journeys and custom challenges to unified auth methods.
Use device signals and risk scoring alongside Aortem session and policy controls.