edik

Secures the backend AND the frontend with ssl when you are logged in. If a user logs in and calls a http site you will be redirected to the equivalent https site. You do not have to manually define <code>FORCE_SSL_ADMIN</code> in the <code>wp-config.php</code>. The authentication cookies will be ssl secured.
<h4>Warning</h4>
There is no protection against ssl leaks. If you follow a http link, a <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack" rel="nofollow ugc">men in the middle</a> could, for example, see which site you enter.
But he cannot steal your login session! 😀

Secured Users Front

Secures the backend AND the frontend with ssl when you are logged in

tronhammer

This plugin will mimic a keep-alive ping by utilizing jQuery to perform an ajax request to the current page, which will update 
the session token tied to PilotPress and or any other system attached using PHP built in sessions. Session Slap will also provide 
a settings interface to allow admins to configure details relating to interval amount (which is defauled to 5 minutes less than the 
session.maxlifetime set in php.ini).
A few notes about the sections above:
<ul>
<li>Configuration options are available in the Settings -> Session Slap menu.</li>
<li>Updates built in PHP sessions only.</li>
<li>Attempts to access session.maxlifetime ini settings, but will default to 24 minutes if not available.</li>
</ul>

Session Slap

Session Slap mimics a keepalive ping by making an AJAX request to the current page to refresh active session timestamp.

Secured Users Front vs Session Slap