This is the master epic for the changes required to accomplish jetpack sign-in with self-hosted credentials.

Changes in FluxC:

• #1402 - Fetch jetpack_user_email param from from the xmlrpc wp.getOptions endpoint and cache locally. (PR: #1403)

Changes in Login library:

• Step 1: Fetch Jetpack e-mail address for flowing through Magic Links: (PR: Jetpack sign in - Step 1: Fetch Jetpack e-mail address for flowing through Magic Links #1483 )
  • Revert existing logic of validating site url from FETCH_CONNECT_SITE_INFO endpoint and use the FETCH_WPCOM_SITE_BY_URL endpoint and initiate the discovery process.
  • Add new button to email screen to Login via site credentials.
  • When site credentials are clicked:
    • If jetpack is installed/active/connected: call the wp.getOptions endpoint to fetch the jetpack_user_email and store in SiteModel and rRedirect to the request magic link screen.
    • If jetpack NOT installed/active/connected: Redirect to Jetpack required screen.
• Step 2: Initiate verification email for the jetpack connected email address. (PR: Issue/1482 step2 magic link signin changes #1498 )
• Step 3: Add Track events for the new buttons/views.
• Step 4: Handle discovery error scenarios for Woo. (PR: Issue/1482 step3 handle discovery error changes #1515 )
  • This includes creating a base class that handles the discovery process and provides an option for the calling class to handle the errors as they see fit.
  • One of the tasks include porting over changes from the LoginSiteAddressFragment to utilise this base class.