The

continue_with

attribute in the response of the registration flow is designed to contain a list of actions that could follow the registration flow. For example, it could contain a reference to the verification flow created as part of the user's registration or the token of the session. However, if the

continue_with

attribute is always null, it could be due to the following reasons: 1. Verification is not enabled: The

continue_with

field with the

verification_ui

action is only present if verification is enabled and the identity schema defines at least one verifiable address. 2. No next actions are required: The

continue_with

field lists possible actions the user might need to take next. If no such actions are required, this field could be null. If you expect the

continue_with

field to contain certain actions and it's always null, you might want to check your configuration and ensure that the necessary conditions for those actions are met. For more details, you can refer to the [Ory API Reference](https://www.ory.sh/docs/reference/api) and the [Ory Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-settings#show-verification-form-after-updating-a-verifiable-address).

To define next actions on a successful registration, you can use Ory's hooks and actions. For instance, you can use the

session

action to sign in the user immediately after they successfully register. This can be done by enabling the

session

action in your configuration. Here are the steps to enable the

session

action: 1. Sign in to the Ory Console and select [Authentication Settings](https://console.ory.sh/projects/current/auth). 2. Toggle Sign In After Registration. 3. Click Save. Alternatively, you can use the Ory CLI to enable this action:

bash ory patch identity-config {project-id} \    --add '/selfservice/flows/registration/after/hooks/0/hook="session"'

This action modifies the HTTP response, so no other hooks can be executed after the

session

action. If you want to trigger multiple actions that modify the HTTP response in your setup, make sure that

session

is triggered last. For more information, refer to the [Ory Documentation](https://www.ory.sh/docs/actions/session). If you want to show the verification flow directly after the user has registered, you can refer to the [registration documentation](https://www.ory.sh/docs/identities/sign-in/actions#show-verification-after-successful-registration). Remember, the actions you can define depend on your specific requirements and the capabilities provided by Ory.

The

show_verification_ui

hook is used to show the verification UI after successful registration. However, it's important to note that the

continue_with

field with the

verification_ui

action will only be present if verification is enabled and the identity schema defines at least one verifiable address. If you have set the

show_verification_ui

hook but the

continue_with

field is still null, it could be because: 1. Verification is not enabled: Make sure that you have enabled verification in your Ory configuration. 2. No verifiable address is defined: The identity schema must define at least one verifiable address for the

verification_ui

action to be triggered. 3. The

show_verification_ui

hook has no effect for API and SPA clients: As per the [Ory Documentation](https://www.ory.sh/docs/identities/sign-in/actions#show-verification-after-successful-registration), the

show_verification_ui

hook does not affect API and SPA clients. If you have ensured all of the above and the issue persists, it might be a good idea to check for any errors in your configuration or consult the [Ory Community](https://community.ory.sh/) for further assistance.

For Single Page Applications (SPA) or API clients, the response from the registration endpoint contains a

continue_with

field. This field lists possible actions the user might need to take next. For example, an object containing the ID of the verification flow created as part of the settings flow. Here is an example of how the response might look:

json {    "continue_with": [    {    "action": "verification_ui",    "flow": {    "id": "d859f6af-1dfe-453e-9320-d572e10edeea",    "verifiable_address": "[[email protected]](<https://www.ory.sh/cdn-cgi/l/email-protection>)"    }    }    // Other items    ]   }

You can use the ID in the

flow

object to fetch the verification flow information, using the

getVerificationFlow

API method. Here is an example of how you can do this in TypeScript:

typescript import { Configuration, FrontendApi } from "@ory/client"      const frontend = new FrontendApi(    new Configuration({    basePath: `https://${process.env.ORY_PROJECT_SLUG}.<http://projects.oryapis.com|projects.oryapis.com>`,    }),   )      export async function getVerification(id: string) {    return await frontend.getVerificationFlow({    id,    })   }

For more information, refer to the [Ory Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-settings#show-verification-form-after-updating-a-verifiable-address) and the [Ory API Reference](https://www.ory.sh/docs/kratos/bring-your-own-ui/custom-ui-basic-integration#get-verification-flow).

If the

continue_with

field is always null, it could be due to the following reasons: 1. Verification is not enabled: The

continue_with

field with the

verification_ui

action is only present if verification is enabled and the identity schema defines at least one verifiable address. 2. No next actions are required: The

continue_with

field lists possible actions the user might need to take next. If no such actions are required, this field could be null. If you expect the

continue_with

field to contain certain actions and it's always null, you might want to check your configuration and ensure that the necessary conditions for those actions are met. For more details, you can refer to the [Ory API Reference](https://www.ory.sh/docs/reference/api) and the [Ory Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-settings#show-verification-form-after-updating-a-verifiable-address).

New message text here

Yes, you can connect multiple hooks in Ory. Hooks are used to run custom logic before or after certain events, such as login, registration, account recovery, account verification, or user settings update. For example, you can use the

session

action to sign in the user immediately after they successfully register. You can also use the

revoke_active_sessions

action to revoke all other active sessions of the user on successful login. Here is an example of how you can configure multiple hooks:

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

In this example, the

session

hook is triggered after successful registration, and the

revoke_active_sessions

hook is triggered after successful login. However, it's important to note that the

session

action modifies the HTTP response, so no other hooks can be executed after it. If you want to trigger multiple actions that modify the HTTP response in your setup, make sure that

session

is triggered last. For more information, refer to the [Ory Documentation](https://www.ory.sh/docs/actions/session) and the [Ory Hooks Documentation](https://www.ory.sh/docs/kratos/hooks/configure-hooks#available-actions).

To create a session after setting up Multi-Factor Authentication (MFA), you can use the

session

hook. However, the process of setting up MFA and creating a session after it is completed involves several steps and depends on the specific MFA method you're using. Here's a general outline of the steps you might need to follow: 1. Set up MFA: Depending on the MFA method you're using (e.g., TOTP, SMS, etc.), you'll need to set up the MFA flow. This typically involves initiating the MFA flow, verifying the MFA code, and then completing the MFA setup. You can refer to the [Ory Documentation](https://www.ory.sh/docs/kratos/mfa/mfa-via-sms#integration) for more details on setting up MFA. 2. Create a session after MFA setup: After the MFA setup is completed, you can use the

session

hook to create a session. This can be done by adding the

session

hook to your configuration. Here's an example:

yaml selfservice:     flows:       mfa:         after:           totp:             hooks:               - hook: session

In this example, the

session

hook is triggered after successful MFA setup using TOTP. Please note that this is a general guide and the exact steps and configuration might vary depending on your specific requirements and setup. Also, the

session

action modifies the HTTP response, so no other hooks can be executed after it. If you want to trigger multiple actions that modify the HTTP response in your setup, make sure that

session

is triggered last. For more information, refer to the [Ory Documentation](https://www.ory.sh/docs/actions/session) and the [Ory Hooks Documentation](https://www.ory.sh/docs/kratos/hooks/configure-hooks#available-actions).

Currently, Ory Kratos does not support a built-in MFA setup hook that can be added to the login after flow. The hooks available in Ory Kratos are

session

,

revoke_active_sessions

, and

verification

as per the [Ory Hooks Documentation](https://www.ory.sh/docs/kratos/hooks/configure-hooks#available-actions). However, you can implement MFA setup as part of your application logic. After a successful login, you can redirect the user to an MFA setup page in your application. Once the user has successfully set up MFA, you can then create a session. Here's a general outline of how you can implement this: 1. Login: Implement the login flow as per the [Ory Login Flow Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-login). 2. Redirect to MFA Setup: After successful login, redirect the user to an MFA setup page in your application. 3. MFA Setup: Implement the MFA setup as per the [Ory MFA Documentation](https://www.ory.sh/docs/kratos/mfa/mfa-via-sms#integration). 4. Create Session: Once the user has successfully set up MFA, create a session using the

session

hook. Remember, this is a general guide and the exact steps and configuration might vary depending on your specific requirements and setup.