ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Diagnose and fix email verification failures in Ory Kratos. Learn how to troubleshoot SMTP misconfigurations, schema errors, and network blocks to ensure users receive registration emails.
Kratos provides a declarative, self-service account recovery flow that eliminates custom password reset code. Two strategies (link or code), single-use tokens, automatic session issuance — all configured in YAML. Here's how to adopt it and where the limits are.
Ory Kratos uses one JSON Schema document as the source of truth for identity traits, driving both server-side validation and self-service form rendering. Here's how it works, with a worked example and the migration trap to avoid.
How Ory Kratos' code method and verification flow enable passwordless, email-verified authentication — with honest config pointers, verification steps, and the trade-offs that matter.
Decide whether to use cookie‑based or token‑based sessions in Ory Kratos. Compare security, cross‑domain support, and implementation steps in a compact decision table, then walk through a concrete config and validation.
Learn how Ory Kratos decouples identity management from application logic using a headless architecture, state-machine flows, and JSON schemas.
Step‑by‑step guide to enable Ory Kratos self‑service registration with email verification, including config snippets, verification checks, and recovery actions.
Goal: configure Ory Kratos self‑service login alerts so that genuine credential‑stuffing attacks trigger notifications while routine low‑volume errors do not flood the alert channel. Current metrics expose kratos_selfservice_flow_error_total labeled by flow type and strategy, but each failed attempt increments the counter individually. Operators must decide
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
ory
prometheus