mortenf

<p>This plugin adds optional per-page user name and password protection, implemented using standard HTTP protocol authorization headers, thus triggering the standard user/password dialog of the browser, and making it possible to make the browser store the credentials.</p>
<p>Subpages of a protected page are protected with the same user name and password as their parent.</p>
<p>Protected pages and their subpages do not show up in menus, search results and page lists.</p>
<h4>Usage</h4>
<ol>
<li>When editing a page, locate the section titled “Page Protection” (probably located near the bottom of the right sidebar).</li>
<li>Check the box “Protect page and subpages”, and provide a user name and password combination.</li>
<li>Optionally, check the box “Make page and subpages searchable”, if you want the page and its subpages turn up in search results, but only with their title, not their content.</li>
<li>Save your page.</li>
</ol>
<h3>License</h3>
<p>Copyright (c) 2009 Morten Høybye Frederiksen <a href="mailto:morten@wasab.dk" rel="nofollow ugc">morten@wasab.dk</a></p>
<p>Permission to use, copy, modify, and distribute this software for any<br />
purpose with or without fee is hereby granted, provided that the above<br />
copyright notice and this permission notice appear in all copies.</p>
<p>THE SOFTWARE IS PROVIDED “AS IS” AND THE AUTHOR DISCLAIMS ALL WARRANTIES<br />
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF<br />
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR<br />
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES<br />
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN<br />
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF<br />
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.</p>


Page Protection

Protect pages and their subpages with user name/password, and keep protected pages from showing up in menus, search results and page lists.

Andrew Norcross

Jason Coleman

<p>WP Bouncer restricts the number of simultaneous logins for the same WordPress user account. The plugin’s goal is to deter people from sharing their login credentials for your site, which is especially important for a paid membership, premium content, or eLearning site.</p>
<h3>How WP Bouncer Protects Shared User Logins</h3>
<ul>
<li>The plugin stores a random <code>FAKESESSID</code> for each user when they log in.</li>
<li>If a user is logged in, on each page load (init hook), WP Bouncer checks if the <code>FAKESESSID</code> stored in the user’s cookies is the same as the last login stored in a transient (<code>fakesessid_user_login</code>).</li>
<li>If the two values do no match, WP Bouncer logs the user out and redirects them to the WordPress login page or a custom page using the wp_bouncer_redirect_url filter.</li>
</ul>
<p>If the WP_BOUNCER_HEARTBEAT_CHECK is defined to true, JavaScript will be loaded to bounce users when a new user logs in with the same login. This is useful for sites with page caching.</p>
<p>Admininstrator accounts or any users with the “manage_options” capability are excluded from bounces.</p>
<h3>Or, Allow a Specific Number of Active Sessions</h3>
<p>By default, WP Bouncer only allows one session per user.</p>
<p>You can use this plugin to offer bulk memberships to corporate, education, or other group-type customers via a shared login.</p>
<p>Use the <code>wp_bouncer_number_simultaneous_logins</code> filter to allow a defined number of active “sessions”.</p>
<p><a href="https://www.paidmembershipspro.com/limit-user-active-sessions/" rel="nofollow ugc">View the Recipe</a></p>
<h3>Example Use Cases for WP Bouncer</h3>
<ul>
<li>User A logs in as “user”. Their <code>FAKESESSID</code>, say “SESSION_A” is stored in a WordPress option.</li>
<li>User B logs in as “user”. Their <code>FAKESESSID</code>, say “SESSION_B” is overwrites the stored WordPress option.</li>
<li>User A tries to load a page on your site, WP Bouncer catches them and logs them out, redirecting them to the warning message.</li>
<li>User B can browse around the site as normal… unless…</li>
<li>User A logs in again as “user”. Their <code>FAKESESSID</code>, “SESSION_A_v2” is stored in the WordPress option.</li>
<li>Now user B would be logged out if they load another page.</li>
</ul>
<h3>Hooks and Filters</h3>
<ul>
<li><code>wp_bouncer_ignore_admins</code> filter: if returning false even admins will be bounced.</li>
<li><code>wp_bouncer_redirect_url</code> filter: can be used to change the URL redirected to after being bounced.</li>
<li><code>wp_bouncer_number_simultaneous_logins</code> filter: can be set to limit logins to a number other than 1. 0 means unlimited logins.</li>
<li><code>wp_bouncer_login_flag</code>: runs right before bouncing (can be used to potentially stop the bouncing).</li>
<li><code>wp_bouncer_session_ids</code> hook: used to filter session ids when saving them. Passes $session_ids, $old_session_ids (before any were removed/bounced), and the current user’s ID as parameters.</li>
<li><code>wp_bouncer_session_length</code> hook: used to filter how long the session ids transients are set. This way, you can time the transients to expire at a specific time of day. Note that the transient is saved on every page load, so if you set it to 5 minutes, it’s going to push it out 5 minutes on every page load. You should try to set it to (the number of seconds until midnight) or something like that.</li>
</ul>
<h3>Support the Plugin Authors</h3>
<p>If you like this plugin, please check out Jason’s work with <a href="https://www.strangerstudios.com" rel="nofollow ugc">Stranger Studios</a> and <a href="https://www.paidmembershipspro.com" rel="nofollow ugc">Paid Memberships Pro</a> and <a href="http://andrewnorcross.com/" rel="nofollow ugc">Andrew’s work at his personal site</a>.</p>


WP Bouncer – Limit Simultaneous Logins

Deter members from sharing login credentials: restrict simultaneous logins for the same user.

Page Protection vs WP Bouncer – Limit Simultaneous Logins