Decoupling Identity: Managing User Flows with Ory Kratos
Learn how Ory Kratos decouples identity management from application logic using a headless architecture, state-machine flows, and JSON schemas.
Loading…
ReadMeFeed / Community knowledge
#ory-kratos
Real questions. Useful conversations. Find the people who know your stack.
Configure Ory Kratos Self‑Service Registration with Email Verification
Step‑by‑step guide to enable Ory Kratos self‑service registration with email verification, including config snippets, verification checks, and recovery actions.
oryOry Kratos Schema Migrations: Version Rollback Compatibility
Database Schema Transition Ory Kratos manages identity data using a SQL database, where schema updates are applied via the ory migrate sql command during version transitions. While the identity attributes are stored in a flexible JSONB format in PostgreSQL, the underlying table structures are subject to version-specific migrations. Migration Constraints Curr
Session cookie SameSite=None limits in Ory Kratos v0.11
Goal Ensure that a single‑page application hosted on a subdomain can maintain an authenticated session after upgrading Ory Kratos from v0.10.5 to v0.11+, while the service runs on PostgreSQL 12+. Constraints and uncertainty Kratos v0.11+ sets the session cookie with SameSite=None and a new name ending in an underscore (ory_kratos_session_). Browsers only hon
ORY Kratos registration fails in production PostgreSQL due to missing verification_token column
The ORY Kratos self‑service registration endpoint works correctly when backed by a local SQLite database, but returns a 500 Internal Server Error in a production PostgreSQL deployment. In the SQLite environment the ORM automatically creates the required verification_token column, masking the missing migration step, whereas the PostgreSQL schema lacks this co
SQL vs SQLite for Ory Kratos Dev: Speed vs Production Parity
The goal is to create a repeatable, container‑based development environment for Ory Kratos that starts quickly while still giving confidence that database migrations and schema will behave identically in production. Using the SQLite backend eliminates the need for a separate database service, giving near‑instant container start and allowing the database file
sqlite