Bug ID 497100: APM Migrates to Google reCAPTCHA API Version 2.0

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1

Fixed In:
13.0.0

Opened: Dec 17, 2014
Severity: 3-Major

Symptoms

Google introduced reCAPTCHA API v2 in December 2014. The v2 API will not work with API key pair generated for v1 API. With APM migrating to reCAPTCHA v2, the key pair that works with previous releases of the APM will stop functioning after upgrade. Google recommends sites that are using v1 API to register new keys and upgrade to v2. (See https://developers.google.com/recaptcha/docs/faq)

Impact

Users will not be able to log in.

Conditions

When key pair generated for v1 API is used in the reCAPTCHA configuration.

Workaround

None

Fix Information

N/A

Behavior Change

Before upgrade, admin is required to register a new key pair with Google. After upgrade, the "secret" and "site key" fields on the reCAPTCHA admin UI are populated with the old keys. Replace the old keys with the new keys obtained from Google. Furthermore, the "Verification URL", "Challenge URL", and "Noscript URL" fields are populated with the URLs for Google reCAPTCHA v2 service, not those that were specified before the upgrade. If a virtual server has been configured for v1 verification using HTTPS, the virtual server needs to add client side SSL profile and the "Verification URL" field should point to the virtual server. Moreover, the "CAPTCHA Theme" is obsolete and is replaced by v2 CAPTCHA render configuration parameters with the following default values: Data Theme = Light Data Type = Image Data Size = Normal