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

zaus

Insert cookie, session, page, or other kinds of values dynamically into Gravity Forms fields.
Similar to how <a href="https://wordpress.org/plugins/forms-3rdparty-dynamic-fields/" rel="ugc">Forms: 3rdparty Dynamic Fields</a> can insert dynamic values into the 3rdparty submission.

Gravity Forms Dynamic Fields

Dynamically fill fields with session, cookie, or other values, based on 'Forms: 3rdparty Dynamic Fields'.

Secured Users Front vs Gravity Forms Dynamic Fields