Protect Dashboard: Add the Login protection section

[enejb]

Fixes JETPACK-2958

Part of JETPACK-2883, JETPACK-2887

Proposed changes

• Stacked on Protect Dashboard: Add tabbed layout and section framework #53190.
• Adds the Login protection section to the flag-gated Protect dashboard (sections/login-protection/ and sections/class-jetpack-protect-dashboard-login-protection.php).
• Overview card: an "N of M on" badge (neutral when no method is available), the locale-formatted all-time blocked login attempt count while brute force protection is on, and one row per method (brute force protection, account protection, WordPress.com login) marked On, Off or Unavailable. The badges follow live module state once settings load, and "Configure login protection" switches to the Settings tab.
• Settings card, in three parts:
  • Brute force protection: the protect toggle (disabled when the module is unavailable), plus the "Always allow specific IP addresses" toggle and list, with a button that adds the visitor's own IP.
  • Account protection: the account-protection toggle (disabled when the module is unavailable).
  • WordPress.com login: the sso toggle, plus "Match accounts using email addresses" and "Require Two-Step Authentication". As in Jetpack Settings, the sso toggle is disabled without a connected owner or in offline mode, and turning it off asks for confirmation first. Both options are disabled while SSO is off. When a filter or constant forces an option, the toggle is locked, shows the value SSO actually applies, and help text says so.
• PHP state: module state for protect, account-protection and sso, the jetpack_protect_blocked_attempts count (always sent, formatted with number_format_i18n()), whether SSO can be turned on (connected owner, not offline), the SSO locks (each Helpers call guarded with method_exists) and the effective SSO values (Helpers::match_by_email(), Helpers::is_two_step_required()), and the current IP. The section adds no REST routes of its own and uses jetpack/v4/settings.

Related product discussion/links

• Protect Dashboard: Add a feature-flagged module that takes over the Protect page #53182, Protect Dashboard: Add tabbed layout and section framework #53190

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• Build and sync Jetpack to a connected test site, then run:

  • wp companion feature-flag enable jetpack-protect-dashboard (or force the jetpack-protect-dashboard flag on with the jetpack_feature_flag_enabled_jetpack-protect-dashboard filter)
  • wp eval 'Jetpack_Options::delete_option("available_modules");'
  • wp jetpack module activate protect-dashboard
  • wp jetpack module activate protect, then the same for account-protection and sso

• Go to Jetpack › Protect (admin.php?page=jetpack-protect). Check that the Login protection card shows "3 of 3 on", "All-time blocked login attempts", and the three methods marked On.

• Click "Configure login protection". The Settings tab should open, with three subsections under Login protection.

• Turn "Match accounts using email addresses" off, then back on. Each change should save with a 200 POST to jetpack/v4/settings.

• Turn on "Always allow specific IP addresses", click "Add my IP address", then click Save. Check that jetpack_waf_ip_allow_list now holds your IP.

• Turn off "Allow users to log in with their WordPress.com account". A confirmation dialog should appear; Cancel leaves SSO on, "Turn off" saves it. The two options under it should then become disabled. Go back to Overview: the badge should now read "2 of 3 on" and the WordPress.com login row should say Off.

• Locked option: add an mu-plugin with add_filter( 'jetpack_sso_require_two_step', '__return_true' ); and reload. "Require accounts to use WordPress.com Two-Step Authentication" should be on and disabled, with help text saying it is enforced. Remove the mu-plugin afterwards.

Review follow-ups

Fixed:

• An enforced Two-Step (or match-by-email) setting no longer shows as off: PHP sends the effective values and locked toggles render them.
• The blocked count is always sent, so turning brute force on from Settings no longer shows 0 for a non-zero count; it is locale-formatted.
• Module toggles respect available, and the SSO toggle needs a connected owner and no offline mode, as in Jetpack Settings.
• Turning SSO off asks for confirmation (AlertDialog from @wordpress/ui).
• The badge is neutral for "0 of 0 on"; the settings link text is sentence case.

Deferred:

• Heading structure: the subsection h3s sit under the card title, which ProtectCard (foundation) renders as a span; the fix belongs in ProtectCard (render the title as h2).
• Jetpack Settings shows an SSO feedback survey after disabling; not ported, since it needs the connection user data and a survey URL that are out of scope here.
• Allow-listing a proxy IP via "Add my IP address" is pre-existing behaviour shared with Jetpack Settings and the Protect plugin.

Screenshots

Overview → Login protection card:

Settings → Login protection card:

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the add/protect-dashboard-login-protection branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/protect-dashboard-login-protection

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

Cannot generate coverage summary while tests are failing. 🤐

Please fix the tests, or re-run the Code coverage job if it was something being flaky.

Full summary · PHP report · JS report