Install the Aortem Flutter and Dart SDK
Get the core package into your app, configure environment values, and attach only the provider adapters your deployment requires.
Flutter package installation
Use the Flutter package in application clients that need redirect handling, session storage, and provider launch orchestration.
Pure Dart package installation
Use the Dart package for server-side tooling, CLIs, and non-Flutter runtimes that need token exchange and session inspection.
Environment setup
Keep configuration declarative. The SDK should only receive client-side identifiers, redirect URIs, and provider registry values that are already validated by your deployment pipeline.
- Set `AORTEM_CLIENT_ID` and the platform-specific redirect URI per environment.
- Separate staging and production tenants to avoid token issuer collisions.
- Inject provider enablement through configuration instead of branching application code.
Provider packages
Provider adapters stay thin by design. They should translate provider-specific configuration into the common auth contract rather than expose a second SDK surface to the application layer.
| Provider | Category | Adapter package | Guide |
|---|---|---|---|
| Firebase | Managed identity | aortem_auth_firebase | Open docs |
| Microsoft Entra ID | Enterprise identity | aortem_auth_entra_id | Open docs |
| AWS Cognito | Cloud identity | aortem_auth_cognito | Open docs |
| Auth0 | Developer identity | aortem_auth_auth0 | Open docs |
| Okta | Workforce identity | aortem_auth_okta | Open docs |
| Magic | Passwordless identity | aortem_auth_magic | Open docs |
| Stytch | Authentication platform | aortem_auth_stytch | Open docs |
| Ping Identity | Enterprise identity | aortem_auth_ping | Open docs |
| Transmit | Customer identity | aortem_auth_transmit | Open docs |
| Fingerprint | Device intelligence | aortem_auth_fingerprint | Open docs |