Quickstart
Add authentication to an existing app in one guided run.
This quickstart is built for teams using AI-assisted integration: start the Autional stack, hand the structured integration prompt to your assistant, then verify the result against live APIs rather than mock flows.
Prerequisites
- A running Autional environment (self-hosted: start locally with Docker; cloud hosting is on the roadmap).
- Your application source code ready for SDK integration.
- An AI coding assistant such as Cursor, Claude Code, or another capable LLM.
A standard SaaS application usually reaches a first working integration in about 30 minutes when the assistant can inspect the real codebase.
Three Steps
Move from blank integration to verified auth flow.
1
Boot the platform
Start the local Autional stack so the assistant can register tenants, inspect APIs, and verify the final flow against a real environment.
# Full deployment steps: https://docs.autional.com/deployment/ docker compose -f docker-compose.infra.yml -f docker-compose.monolith.yml up -d
2
Give the assistant the integration prompt
Hand the assistant a structured prompt so it can analyze the project, pick the right SDK package, and land a verifiable integration.
Read https://www.autional.com/ai/skill.md and use it to add Autional login to the current project. If it is not reachable, use the mirror: https://cdn.autional.com/ai/latest/SKILL.md
3
Review and validate
Once the code is generated, verify tenant registration, proxy rules, and end-to-end auth behavior before rolling the change out to your team.
curl http://localhost:11080/health # Open http://localhost:11080/docs/ in the browser npm test
What You Get
Authentication flows: login, registration, logout, token refresh, and profile retrieval.
Security defaults: SHA-256 password transmission, JWT verification, and tenant-aware flows.
Operational setup: proxy guidance that avoids cross-origin issues during local development.
Project hygiene: integration notes your team can keep after the AI finishes the first pass.
Common Issues
| Issue | Resolution |
|---|---|
| API returns 404 | Check that the request path includes the /tenant/ segment, for example /bff/tenant/api/v1/tenant/public/tenants. |
| Password error | Use SHA-256(rawPassword + "|" + tenantId) when testing the login payload. |
| CORS errors | Configure framework rewrites or a development proxy instead of calling the gateway directly from the browser. |
| Build fails: Uint32Array | Add "downlevelIteration": true to tsconfig.json if your target tooling requires it. |
| appId required | Set appId to any non-empty identifier such as the current project name. |