By default, registration does NOT create a login session. After a successful registration, you’d still need to run the login flow unless you enable “auto-login after registration” (the session hook). With that hook enabled, Kratos returns a session (and sets the session cookie for browser flows), so you don’t need to call the login APIs. ([Successful registration](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration)). - API clients: response includes identity; with the session after-hook, it also includes session and session_token ([API clients](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#api-clients)). - Client-side/browser: 200 OK with identity; with the session hook, a Set-Cookie is returned alongside redirect and session info ([Client-side browser clients](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#client-side-browser-clients)). - You can toggle this in Console: Authentication → Registration → “Sign In After Registration” ([Log in users after registration](https://www.ory.sh/docs/identities/sign-in/actions#log-in-users-after-registration)).

Here are the supported ways to enable “auto-login after registration” (the session hook): Option A — Ory Console (Ory Network) - Go to Authentication → Registration in the Ory Console. - Toggle “Sign In After Registration”. - Save. (This enables the session action after registration) ([Log in users after registration](https://www.ory.sh/docs/identities/sign-in/actions#log-in-users-after-registration), [Sign in after registration](https://www.ory.sh/docs/actions/session)). Notes: - If you also require verified email for login, the session action will sign the user in once right after registration, but they must verify before future logins ([Sign in after registration](https://www.ory.sh/docs/actions/session)). Option B — Ory CLI (Ory Network) - Enable the session hook for all registration methods:

ory patch identity-config --project <project-id> --workspace <workspace-id> \     --add '/selfservice/flows/registration/after/hooks/0/hook="session"'

([Sign in after registration](https://www.ory.sh/docs/actions/session)). - If you need to target a specific method (e.g., code or oidc), patch the method-specific path. Example reported workaround for code:

ory patch project <project-id> --replace '/services/identity/config/selfservice/flows/registration/after/code/hooks=[{"hook":"session"}]'

(From a past issue where Console didn’t expose this setting; use CLI if needed) ([Configure session after Registration via code in Console](https://github.com/ory/network/issues/340)). Option C — Self-hosted Kratos (kratos.yml) - Add the session hook in the registration after-hooks for the methods you use:

selfservice:     flows:       registration:         after:           password:             hooks:               - hook: session           oidc:             hooks:               - hook: session           # For passwordless code, add:           code:             hooks:               - hook: session

([Successful registration](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration), [Social sign-in config note](https://www.ory.sh/docs/self-hosted/kratos/configuration/oidc)). Operational tips - Session hook must run last because it modifies the HTTP response; no actions after it will execute. If mixing with webhooks/actions, ensure session is last in order ([Troubleshoot Ory Actions Webhook issues](https://www.ory.sh/docs/troubleshooting/troubleshoot-actions), [Sign in after registration](https://www.ory.sh/docs/actions/session)). - OIDC: Always enable session after OIDC registration to avoid forcing a separate login step ([Successful registration](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration)). - Browser flows: With session enabled, Kratos sets the session cookie on redirect; API/native clients receive session and session_token in the response ([Successful registration](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration), [Sign in after registration](https://www.ory.sh/docs/actions/session)).

Here are the steps for a self‑hosted Kratos + Hydra setup to enable “auto‑login after registration” (session hook): 1) Configure Kratos (kratos.yml) - Add the session hook under registration “after” for each method you use (password, oidc, code, etc.). Ensure it’s the last hook if you use multiple actions.

yaml selfservice:   flows:     registration:       after:         password:           hooks:             - hook: session         oidc:           hooks:             - hook: session         code:           hooks:             - hook: session

- Rationale and examples for password/oidc (and why OIDC should always have session) are documented here (Successful registration). The OIDC config page also reminds to add the session hook under after/oidc/hooks to avoid requiring an extra login (Social sign-in). The session action modifies the HTTP response, so no hooks can run after it; place it last (Sign in after registration; Troubleshoot Actions). Citations: (["Successful registration"](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration), ["Social sign-in"](https://www.ory.sh/docs/self-hosted/kratos/configuration/oidc), ["Sign in after registration"](https://www.ory.sh/docs/actions/session), ["Troubleshoot Actions"](https://www.ory.sh/docs/troubleshooting/troubleshoot-actions)) 2) Restart Kratos - Apply the updated configuration by restarting your Kratos service so the hooks take effect (general config practice; the guide shows config changes are applied via service reload/restart) (["Configure User Interface" guide](https://www.ory.sh/docs/kratos/guides/deploy-kratos-example#configure-user-interface)). 3) Verify behavior - Browser flow: After successful registration, Kratos issues a 303 redirect and sets the session cookie (no separate login needed) when the session hook is enabled (Successful registration). - Native/API flow: The response includes session and session_token when session is enabled (Sign in after registration). Citations: (["Successful registration"](https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration), ["Sign in after registration"](https://www.ory.sh/docs/actions/session)) Notes for Hydra integrations - No special Hydra change is required for this feature. Kratos creates the user session; your app can then continue into the Hydra login/consent as usual. If you are in a Hydra‑initiated login/registration, make sure your Kratos return URLs and Hydra URLs are set correctly so redirects flow back to Hydra after the session is created (see your existing Hydra/Kratos URL wiring). The core requirement here is the Kratos session hook (above). The registration “after/session” behavior is entirely on the Kratos side (Successful registration; Sign in after registration).

Use these docs: - Enable auto-login (session action) in self-hosted Kratos config (after hooks for registration): “Successful registration” (https://www.ory.sh/docs/kratos/self-service/flows/user-registration#successful-registration). - OIDC/self-hosted note to add session hook under after/oidc/hooks: “Social sign-in” (https://www.ory.sh/docs/self-hosted/kratos/configuration/oidc). - Behavior and caveat that session action must run last: “Sign in after registration” (https://www.ory.sh/docs/actions/session).