Methods
1 to 10 of 10
- Jetpack_SSO_Notices::cant_find_user() – Message displayed when the user can not be found after approving the SSO process on WordPress.com
- Jetpack_SSO_Notices::disable_default_login_form() – When the default login form is hidden, this method is called on the ‘authenticate’ filter with a priority of 30.
- Jetpack_SSO_Notices::error_invalid_response_data() – Error message that is displayed when we are not able to verify the SSO nonce due to an XML error or failed validation. In either case, we prompt the user to try again or log in with username and password.
- Jetpack_SSO_Notices::error_msg_email_already_exists() – Error message displayed when the user tries to SSO, but match by email is off and they already have an account with their email address on this site.
- Jetpack_SSO_Notices::error_msg_enable_two_step() – Error message displayed on the login form when two step is required and the user’s account on WordPress.com does not have two step enabled.
- Jetpack_SSO_Notices::error_msg_identity_crisis() – Error message that is displayed when the current site is in an identity crisis and SSO can not be used.
- Jetpack_SSO_Notices::error_unable_to_create_user() – Error message that is displayed when we were not able to automatically create an account for a user after a user has logged in via SSO. By default, this message is triggered after trying to create an account 5 times.
- Jetpack_SSO_Notices::get_sso_required_message() –
- Jetpack_SSO_Notices::msg_login_by_jetpack() – Message displayed when the site admin has disabled the default WordPress login form in Settings > General > Secure Sign On
- Jetpack_SSO_Notices::sso_not_allowed_in_staging() – Error message that is displayed when the current site is in an identity crisis and SSO can not be used.
