Overview⚓︎
Learn how to install the Authentication Server (AS) and integrate it into your applications.
Components⚓︎
The full server-side nextAuth solution is distributed as Docker images:
ns: the nextAuth Server image, handling all communication with the application and driving the nextAuth API.sfs: the Second Factor Server image, verifying the user's second factor (PIN or biometric).mc: the Message Center image, which proxies push notification to the relevant platform-specific service.
We recommend using your existing infrastructure to host the different images and provide ingress routes to their services. Consult the Network Setup documentation for guidance.
What to install?⚓︎
When using a third-party mobile app with the nextAuth Mobile SDK, it is not necessary to install the mc and sfs images. The third-party app owner will need to run the mc and sfs containers. The mobile app will connect to these containers for second factor verification and messaging. You will need to configure your ns instance to trust the third-party sfs and mc.
In case you are developing your own app, you will need to run the mc and sfs containers and configure your mobile app to use these servers for second factor verification and messaging.
Dependencies⚓︎
The ns, sfs, and mc images all depend on a relational database server (PostgreSQL, MySQL or MariaDB). In addition, the ns also requires access to a Redis instance (optional in single instance setups).
| Dependency | Supported Versions |
|---|---|
| MariaDB | >= 10.5.2 |
| MySQL | >= 8.0 |
| PostgreSQL | >= 9.5 |
| Redis | >= 3.2.6 |
Our default setup provides both of these services as a separate Docker container. For high-availability setups, it is recommended to use a separate HA setup of both the database and Redis.