Any Jetpack site user should be able to log in to the app using their site address.
Only the user who connected the Jetpack plugin is able to log in to the app using their site address.
wp-admin via Users > Add New. Do not connect this user to Jetpack.Thanks to @malinajirka for originally reporting this.
Nice catch!
There is one more variable to consider and that is whether or not the account email address has or does not have a WordPress.com account associated with it.
Using the steps above, if the user does have a WordPress.com account associated with their email address then they are logged in but the Jetpack site is not added (because this user has never connected Jetpack via the WP Admin > Jetpack dashboard). It's possible to go to My Sites > + > Add self-hosted site at this point but it's not super obvious that this needs to be done after logging in. Note that Stats show an error in this scenario. If the user does not have a WordPress.com associated with WordPress.com, then they are shown the Get Started screen (and eventually a Sign Up prompt) as noted in the steps on the issue. (2m46s)
I tested this with the Jetpack SSO setting off to start (the default) and then with it turned on and the results were the same in my tests.
@designsimply That's a very good point, thanks for mentioning it!
The reason that happens is because we are not really using the WordPress.com account to connect to the Jetpack site. Instead, we just assumed the user had already connected before and redirect them to the WordPress.com flow, which is clearly not ideal.
That said, I've just opened a PR that reverts this behavior to what it was before, where a Jetpack site user is always redirected to the Username/Password screen and needs to login with their site credentials. This approach also have some drawbacks, but it should be ok for now, while we consider other alternatives (internal ref: pbArwn-19o-p2#comment-1714). This is also the current behavior on iOS.
Closed by #13065.
Most helpful comment
@designsimply That's a very good point, thanks for mentioning it!
The reason that happens is because we are not really using the WordPress.com account to connect to the Jetpack site. Instead, we just assumed the user had already connected before and redirect them to the WordPress.com flow, which is clearly not ideal.
That said, I've just opened a PR that reverts this behavior to what it was before, where a Jetpack site user is always redirected to the Username/Password screen and needs to login with their site credentials. This approach also have some drawbacks, but it should be ok for now, while we consider other alternatives (internal ref: pbArwn-19o-p2#comment-1714). This is also the current behavior on iOS.