sakurainternet

Auto Login for Sakura Rental Server allows administrators to issue one-time, time-limited auto-login URLs using HMAC signatures. 
This is useful for secure temporary access or system integration.
Features: 
– Secure auto-login with one-time tokens 
– Tokens are HMAC-signed and invalidated after use 
– Token issuance and usage history (up to 100 entries per user) 
– Records IP address and username of the issuer 
– Rate limiting: 1 request per second per IP 
– WP-CLI commands for token generation and history inspection
Example use cases: 
– Temporarily granting admin access 
– Safe automatic login from external systems 
– Keeping an audit log of who issued a token and from where
<h3>Usage</h3>
<h3>Generate a token via CLI</h3>
<pre><code>wp auto-login-for-sakura-rental-server generate <user_id> [–expires=] [–remote_addr=] [–username=]
</code></pre>
Example:
<ul>
<li>Default expiration time: 300 seconds </li>
<li><code>--expires</code> and <code>--username</code> are optional</li>
</ul>
<h3>Check issue history</h3>
Token history is stored in the user meta key <code>sakura_auto_login_history</code>. 
You can check it via WP-CLI:
wp user meta get sakura_auto_login_history
<h3>Auto-login URL format</h3>
<pre><code>https://example.com/?rs_auto_login_token=<64-character HMAC token>
</code></pre>
Visiting the URL will log in as the corresponding user and redirect to the admin dashboard.
<h3>Security Notes</h3>
<ul>
<li>Tokens are invalidated immediately after use (one-time only)</li>
<li>Issue and usage history includes IP address, issuer username, and timestamps</li>
<li>Stored using <code>set_transient()</code> for caching compatibility</li>
<li>HTTPS is strongly recommended</li>
</ul>

Auto Login for Sakura Rental Server

Provides one-time auto-login URLs with HMAC signatures and time limits.

Tyler Shuster

This is a plugin to manage deployment of WordPress sites to one or multiple servers, whether development, staging or production. Add, remove, push to, or pull from environments under Tools -> Deploy.
Requires: 
rsync 
If using ssh and not the command line, must use key-based authentication
Add the following constants to your wp-config.php or add them via the admin interface.
(ENV can be any name of your choosing for your remote environment)
<pre><code>DEPLOY_[ENV]_DB_HOST
DEPLOY_[ENV]_DB_USER
DEPLOY_[ENV]_DB_NAME
DEPLOY_[ENV]_DB_PORT
DEPLOY_[ENV]_DB_PASSWORD
</code></pre>
* Database dsn for the environment 
* Mandatory: Yes except for port (default 3306)
<pre><code>DEPLOY_[ENV]_SSH_DB_HOST
DEPLOY_[ENV]_SSH_DB_USER
DEPLOY_[ENV]_SSH_DB_PATH
DEPLOY_[ENV]_SSH_DB_PORT
</code></pre>
* If you need to connect to the destination database through SSH (you probably do) 
* Mandatory: No, port defaults to 22
<pre><code>DEPLOY_[ENV]_SSH_HOST
DEPLOY_[ENV]_SSH_USER
DEPLOY_[ENV]_SSH_PORT
</code></pre>
* SSH host to sync with Rsync 
* Mandatory: No, port defaults to 22
<pre><code>DEPLOY_[ENV]_PATH
</code></pre>
* Server path for the environment (used to reconfigure the WordPress database) 
* Mandatory: Yes
<pre><code>DEPLOY_[ENV]_URL
</code></pre>
* Url of the WordPress install for this environment (used to reconfigure the WordPress database) 
* Mandatory: Yes
<pre><code>DEPLOY_[ENV]_EXCLUDES
</code></pre>
* Add files to exclude from rsync. List must be separated buy semicolons. 
* Mandatory: No

WP Deploy Flow

This adds functionality that allows developers to pull or push their entire site or only the files from a variety of remote environments.

Auto Login for Sakura Rental Server vs WP Deploy Flow