|
|
| Line 1: |
Line 1: |
| − | Differentiating between humans and bots (computers) is an ever-changing and more challenging task. A number of solutions have been implemented, typically involving increasing obscured text and numbers or images, such as the default 5 character verification of WHMCS.
| + | #REDIRECT [[Google_reCAPTCHA]] |
| − | | |
| − | ==reCAPTCHA Version 2==
| |
| − | As bots and software have become more sophisticated, a common solution was to make the text more difficult to read, which can result in frustrated and lost potential clients. Google's reCAPTCHA set's out to change that. They have created a system that is easy for people, but hard for bots. By using an advanced and more secure risk analysis engine, humans and bots are more effectively differentiated.
| |
| − | | |
| − | The first step in authentication is to ask the user to confirm that they are not a robot by ticking a checkbox. While this sounds simple, Google's risk analysis engine takes a lot into account about how the user came to tick the checkbox, including how the user responds before, during, and after the action. In cases where the engine cannot confidently differentiate, a mobile-friendly verification tool like image selection from a list may be supplied or a CAPTCHA itself.
| |
| − | [[File:ReCPATCHA Configuration.png|thumb|reCPATCHA Key Generation]]
| |
| − | Google's reCAPTCHA may be enabled by following these steps:
| |
| − | # Navigating to '''Setup >> General Settings''', | |
| − | # Selecting the Security tab,
| |
| − | # Choosing the reCAPTCHA Captcha Type radio button,
| |
| − | # Entering the public and private keys [https://www.google.com/recaptcha/admin supplied by Google here].
| |
| − | * For forward compatibility we recommend selecting the Invisible reCAPTCHA option:
| |
| − | More information is available [https://www.google.com/recaptcha/ here].
| |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | Below are some examples of how the reCAPTCHA challenge may be presented to your end users.
| |
| − | | |
| − | http://4.bp.blogspot.com/-wt7yljKcU_8/VH5MJTUCBOI/AAAAAAAAACw/WKqE3ixUUdw/s1600/Recaptcha_anchor%402x.gif
| |
| − | | |
| − | http://4.bp.blogspot.com/-sLrMDmf4gOc/VH5MJRg7VnI/AAAAAAAAACU/svXWqwOpyds/s1600/CAPTCHA.png
| |
| − | | |
| − | http://2.bp.blogspot.com/-3ylGBdjKA08/VH5MJ0jAuYI/AAAAAAAAAC4/m8QhettQP1Y/s1600/cat_captcha.png
| |
| − | | |
| − | http://1.bp.blogspot.com/-pA1LDaLSnWg/VH5MKbOJYxI/AAAAAAAAAC0/2jNt5wF-cJA/s1600/turkey_captcha.png
| |
| − | | |
| − | ==reCAPTCHA Version 1==
| |
| − | In WHMCS versions 5 to 6, a previous implementation of reCAPTCHA was used, referred to as "V1". This service has been discontinued by Google, but our documentation for this remains for archive purposes.
| |
| − | | |
| − | For instructions on migrating from reCAPTCHA v1 to v2, please refer to the [[Google reCAPTCHA]] page.
| |