reCAPTCHA v3 Connector
Use Descope's reCAPTCHA v3 connector to secure your authentication flow. reCAPTCHA is a free google service that protects your site from spam and abuse that uses advanced risk analysis techniques to tell humans and bots apart. This article will go through setting up the connector and including it in your authentication flow.
Note
Descope also supports reCAPTCHA enterprise, if you'd like to learn more about using reCAPTCHA enterprise within Descope, view this tutorial.
Configure reCAPTCHA v3 connector
Descope uses your Google Site and Secret Keys to integrate reCAPTCHA.
Start at your dashboard. Navigate to the reCAPTCHA connector: Dashboard -> Connectors -> reCAPTCHA
Now, complete the required fields:
- Connector name: Custom name for your connector. This will come in handy when creating multiple connectors from the same connector template.
- Site Key: The site key you get from Google. For more information, see here.
- Secret Key: The secret key you get from Google. For more information, see here. And if you'd like, the optional fields:
- Connector description: Describe what your connector is used for.
You can test if your connector's configuration is working properly simply by hitting the Test
button and viewing the Test Results
panel.
Save your configuration by hitting Create.
Add your reCAPTCHA connector to a screen
Navigate to: Dashboard, choose your flow.
Select a screen (likely the first in the flow) in your editor and choose the reCAPTCHA widget in the risk
section.
Drag the widget into the screen. Hit "Done."
Add your reCAPTCHA connector to the flow
Now, back to the flow editor, tap the create button (designated via the +
icon), select Connector, and choose reCAPTCHA.
Click to set down the connector in your flow editor, and connect it at a point that comes after the screen with reCAPTCHA widget that you added in the previous step. Now, hit "Save."
Whenever a user goes through your authentication flow, the reCAPTCHA connector will automatically
run and the risk analysis will now be included in the flow riskScore
and botDetected
condition.