Van Patten Media

<p>Designed to be run in concert with <a href="https://wordpress.org/extend/plugins/ssl-subdomain-for-multisite/" rel="ugc">SSL Subdomain for Multisite</a>.</p>
<p><strong>This plugin <em>depends</em> upon <a href="https://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/" rel="ugc">WPMU Domain Mapping</a>, which must be installed and network activated for this to work.</strong></p>
<h4>What this Plugin does</h4>
<p>If you have the <a href="https://wordpress.org/extend/plugins/ssl-subdomain-for-multisite/" rel="ugc">SSL Subdomain for Multisite</a> plugin installed and network activated, you now have logins and admin happening on <code>https://demo-site.mynetwork.com</code>, while normal site access is on <code>http://demo-site.com</code>.</p>
<p>This works great. Except, once you log in to <code>demo-site.mynetwork.com</code> to do some admin work, then visit the main site, perhaps to post a comment as a logged in WordPress user, you are not logged in on the main site. This means that you can’t, for example, post that comment while logged in — you aren’t logged in there! Other logged-in niceties like the display of the admin bar, or the avoidance of caching, are not available. If you log in again, it logs you in to <code>https://demo-site.mynetwork.com</code> but still you remain not logged in on <code>http://demo-site.com</code>.</p>
<p>This plugin solves this problem by enabling a single sign on (SSO) for both the admin panel and the main site on the custom domain. Upon login, this plugin bounces the user across to the main site to set a cookie there, then bounces them back to the admin panel.</p>
<p>Now, you can work in the admin panel normally, and if you click ‘Visit Site’ from the Admin panel, you go over to the custom domain, where you are also logged in and can perform all actions as normal. Single Sign On!</p>
<h4>(Foolish) Assumptions</h4>
<ol>
<li>
<p>You are using <a href="https://wordpress.org/extend/plugins/wordpress-mu-domain-mapping/" rel="ugc">WPMU Domain Mapping</a> for custom domains on your Multisite network.</p>
</li>
<li>
<p>You have SSL configured for your master domain (e.g. <code>www.mynetwork.com</code>), and for the wildcard <code>*.mynetwork.com</code>. You would like normal site access to happen over the custom domains with HTTP, and all admin and login access over the subdomains of <code>*.mynetwork.com</code> with HTTPS.</p>
</li>
<li>
<p>You have the <code>FORCE_SSL_LOGIN</code> setting in <code>wp-config.php</code> <strong>ON</strong>.</p>
</li>
<li>
<p>You have the <code>FORCE_SSL_ADMIN</code> setting in <code>wp-config.php</code> <strong>OFF</strong>. We’ll handle that — WordPress’ forcing of SSL admins may confuse this plugin.</p>
</li>
</ol>
<p>This plugin was tested with and is intended to be used in concert with <a href="https://wordpress.org/extend/plugins/sso-cross-cookie-for-multisite/" rel="ugc">SSL Subdomain for Multisite</a>.</p>
<h4>Known Issues</h4>
<ul>
<li>The <code>redirect_to</code> parameter is not fully working at present. Sometimes, you will be sent to the root admin page, instead of the specific page you were trying to access. This needs to be improved, as it does compromise the user experience.</li>
<li>
<p>This provides better security than only enabling <code>FORCE_SSL_LOGIN</code> but not <code>FORCE_SSL_ADMIN</code>, since with this plugin and <a href="https://wordpress.org/extend/plugins/sso-cross-cookie-for-multisite/" rel="ugc">SSL Subdomain for Multisite</a>, login and admin are served over HTTPS.</p>
<p><strong>However</strong>, the nature of this setup means that a man-in-the-middle attacker could theoretically impersonate you for the duration of the login session. It is not possible at the moment to avoid this theoretical attack scenario without serving <strong>everything</strong> over HTTPS (making arbitrary custom domain support impossible), or preventing login to the actual custom domain site.</p>
</li>
</ul>


SSO Cross Cookie

Single sign on (SSO) for a custom domain site, where the admin panel is on an SSL-secured subdomain. For WordPress Multisite.

AK Ted

<p>When you activate MU Plugins Tool, a folder named ‘mu-plugins’ is created, if necessary, in your WordPress installation (default ‘WordPress_Root/wp-content/mu-plugins’) and a starter mu-plugin is created. The starter mu-plugin changes the admin footer text once you’ve enabled it through MU Plugins Tool. For more information, see the Codex <a href="https://codex.wordpress.org/Must_Use_Plugins" rel="nofollow ugc">Must-Use Plugins</a> page.</p>
<h3>Future Features – no promises 😉</h3>
<ul>
<li>create, edit & delete MU-plugins with MU Plugins Tool;</li>
<li>upload MU-plugins from your computer;</li>
<li>view a MU-plugin’s code by hovering over the name;</li>
<li>change the MU Plugins Tool menu location, e.g., under ‘Plugins’ or ‘Settings’;</li>
<li>recreate the starter plugin at will</li>
</ul>
<h3>Acknowledgement</h3>
<p>I would like to thank <a href="http://www.presscoders.com" rel="nofollow ugc">David Gwyer</a>, the developer of <a href="https://wordpress.org/extend/plugins/plugin-options-starter-kit" rel="ugc">Plugin Options Starter Kit</a> (POSK). It’s an awesome tool for learning the ins and outs of designing an options page for your plugin. MU Plugins Tool would’ve been much harder to make without POSK as a learning tool.</p>


MU Plugins Tool

MU Plugins Tool allows you to activate or deactivate any MU (must-use) plugins that are installed - on an individual basis or all at once.

SSO Cross Cookie vs MU Plugins Tool