I've run into a problem with the option "Force http/https (Only for original domain)" set to "Yes" and "Administration mapping" left to "domain entered by the user" in combination with Jetpack activated Network wide (don't know if that makes a difference).
This causes some links on the Jetpack admin pages to use the HTTPS protocol even if visited on the mapped domain admin. For example, the buttons "Settings" and "My Jetpack" at the top of the screen, the "Debug" and "Disconnect" links in the footer, or any of the "De/Activate" and "Configure" links on the modules list. Following such a link will cause an infinite loop between HTTPS and HTTP.
Effectively, this cripples control over Jetpack modules and prevents setting up any new connections with WordPress.com or even removing existing ones.
Is there any way to make Domain Mapping (with TLS on the original domain) and Jetpack work together?