Configure your captcha provider

Use the Integrations feature in the Next Identity Console to connect a third-party captcha service that helps detect and block automated bot activity. Captcha protects your application from fraudulent account creation and login attempts without disrupting legitimate users.

By default, Next Identity Google reCaptcha is available, but you can connect an external captcha provider if needed.

• Access to the Integrations feature in the Next Identity Console.

• Appropriate user role with permission to view or edit integrations.

• Credentials for your chosen captcha provider (e.g., API key).

1. Open the Integrations section from the left menu.

2. Locate the Captcha category.

3. Select View Details to see all captcha integrations.

1. In the Captcha Integrations list, select New Integration.

2. Follow the two-step setup process:

   Step 1: Select Provider

   • Choose Google reCaptcha as your provider.

   Step 2: Configure Integration

   • Enter the integration name and required credentials.

   • To make this your default provider, enable the Set as Default option and select the target environments.

3. Select Save to complete the integration setup.

1. In the Captcha Integrations list, locate the integration you want to assign.

2. Select Set Default Provider.

3. In the modal, choose the environment(s) where this integration will be used.

4. Select Save.

Each environment can only have one active provider. Setting a new default replaces the previous one.

1. In the Captcha Integrations list, select the edit button (pencil icon) next to the integration.

2. Update the details (e.g., name, API key).

3. Select Save.

1. In the Captcha Integrations list, select the delete button (trash icon) next to the integration.

2. Confirm the deletion in the dialog.

Note:
You cannot delete an integration currently active in any environment. Unassign it first before deleting.

Once your captcha provider is configured and assigned to an environment, all captcha-based verifications in that environment will be handled through the selected integration. This adds a layer of protection against automated abuse in registration, login, and other user interactions.