r0bodev

<p>Titan Social Login adds OAuth-based sign-in to WordPress so visitors can use their existing social accounts instead of creating new passwords.</p>
<h4>Included providers</h4>
<ul>
<li>Amazon</li>
<li>Facebook</li>
<li>Google</li>
<li>X (Twitter)</li>
<li>Microsoft</li>
</ul>
<h4>Key features</h4>
<ul>
<li>Adds login buttons to the WordPress login, registration, and lost password screens.</li>
<li>Optional social login on comment forms.</li>
<li>Account linking inside WordPress user profiles.</li>
<li>Shortcodes: [tsl_login], [tsl_account_links].</li>
<li>Popup or same-window authentication, configurable for desktop and mobile.</li>
<li>Custom redirect after login or first registration.</li>
<li>Design controls for layout, spacing, labels, and button styles.</li>
<li>Placeholder emails for providers that do not return an email address.</li>
</ul>
<p>This plugin uses external OAuth providers for authentication. See the “External Services” section for details.</p>
<h4>Privacy</h4>
<p>Titan Social Login does not collect or send any usage telemetry. OAuth requests go directly to the enabled provider during login. The plugin stores its configuration in your WordPress database.</p>
<h4>Additional features in the Pro version</h4>
<ul>
<li>30+ OAuth providers including Apple, Discord, GitHub, Steam, Telegram, Twitch, Spotify, and more.</li>
<li>Premium integrations for WooCommerce, BuddyPress, Ultimate Member, and Easy Digital Downloads.</li>
<li>Statistics dashboard to monitor social login performance.</li>
<li>Premium updates and priority support.</li>
</ul>
<p>Pro version and pricing: <a href="https://titan.r0bo.dev/#pro" rel="nofollow ugc">https://titan.r0bo.dev/#pro</a><br />
Demo: <a href="https://titan.r0bo.dev/wp-login.php" rel="nofollow ugc">https://titan.r0bo.dev/wp-login.php</a></p>
<h3>External Services</h3>
<p>Titan Social Login connects to third-party OAuth providers to authenticate users. Requests are made only when an administrator enables a provider and a user clicks a login button.</p>
<p>Data sent during OAuth:<br />
– Authorization request: client_id, redirect_uri, response_type, scope, state<br />
– Token exchange: code, client_id, client_secret (if required), redirect_uri<br />
– Profile request: access_token</p>
<p>Data received from providers:<br />
– Provider user ID, name, email address, and profile picture (when available)</p>
<p>Services used:<br />
– Google OAuth API (accounts.google.com, oauth2.googleapis.com, www.googleapis.com). Terms: https://policies.google.com/terms Privacy: https://policies.google.com/privacy<br />
– Facebook Login (www.facebook.com, graph.facebook.com). Terms: https://www.facebook.com/legal/terms Privacy: https://www.facebook.com/privacy/policy<br />
– Amazon Login (www.amazon.com, api.amazon.com). Terms: https://www.amazon.com/gp/help/customer/display.html?nodeId=508088 Privacy: https://www.amazon.com/gp/help/customer/display.html?nodeId=468496<br />
– Microsoft identity platform (login.microsoftonline.com, graph.microsoft.com). Terms: https://www.microsoft.com/servicesagreement Privacy: https://privacy.microsoft.com/privacystatement<br />
– X (Twitter) OAuth 2.0 (twitter.com, api.twitter.com). Terms: https://twitter.com/en/tos Privacy: https://twitter.com/en/privacy</p>
<p>No external requests are made unless the provider is enabled and a user initiates login.</p>
<h3>License</h3>
<p>PHP code (and any JS that links to WordPress APIs) is licensed under the GNU General Public License v2.0 or later (GPL-2.0-or-later). See /license.txt.<br />
Brand icons in /assets/images/icons are trademarks of their respective owners and are included for identification purposes only. See /THIRD-PARTY-NOTICES.txt.<br />
Trademarks belong to their respective owners; this plugin is not affiliated with or endorsed by them.</p>


Titan Social Login

One-click social login and account linking for Amazon, Facebook, Google, X (Twitter), and Microsoft.

Jesin A

<p>This plugin adds an additional layer of protection for the <strong>wp-login.php</strong> page using <a href="http://en.wikipedia.org/wiki/Digest_access_authentication" rel="nofollow ugc">HTTP Digest Authentication</a> with the PHP <a href="http://php.net/header" rel="nofollow ugc">header()</a> function.<br />
So it doesn’t require configuring web server files like <em>.htaccess</em> or <a href="https://websistent.com/tools/htdigest-generator-tool/" rel="nofollow ugc"><em>.htdigest</em></a> and works on all web hosting environments.</p>
<p><strong>Important:</strong> If you already have a plugin which does HTTP Authentication please deactivate it before activating this plugin. Similarly if you have configured your web server to do HTTP authentication on the wp-login.php file please remove it before using this plugin.</p>
<p>If you are using FastCGI PHP this plugin may keep prompting for the credentials even if you enter the right pair, in this case use the following in your <strong><code>.htaccess</code></strong> file</p>
<pre><code><IfModule mod_setenvif.c>
SetEnvIfNoCase ^Authorization$ "(.+)" PHP_AUTH_DIGEST=$1
</IfModule>
</code></pre>
<h4>Advantages of HTTP Digest Authentication</h4>
<ul>
<li>Digest Authentication is very much safer than HTTP Basic Authentication whose credentials can be easily decoded with a <a href="http://www.base64decode.org/" rel="nofollow ugc">base64 decoder</a>.</li>
<li>From Wikipedia on <a href="http://en.wikipedia.org/wiki/Basic_access_authentication" rel="nofollow ugc">HTTP Basic Authentication</a>:</li>
</ul>
<blockquote>
<p><em>The BA (Basic Authentication) mechanism provides no confidentiality protection for the transmitted credentials. They are merely encoded with BASE64 in transit, but not encrypted or hashed in any way.</em></p>
</blockquote>
<ul>
<li>Digest Authentication on the other hand uses <a href="https://websistent.com/tools/md5-encryption-tool/" rel="nofollow ugc">MD5</a> on the credentials making it “one way” </li>
<li>Uses server and client <a href="http://en.wikipedia.org/wiki/Cryptographic_nonce" rel="nofollow ugc">nonce</a>s to prevent replay attacks</li>
</ul>
<h4>Features of the HTTP Digest Auth plugin</h4>
<ul>
<li>Works using PHP header() function and doesn’t require modification of service config files (like .htaccess, nginx.conf etc)</li>
<li>Supports HTTP credentials for each WordPress user</li>
<li>Clears the HTTP Digest credentials when the user logs out of WordPress (more on this in the FAQ)</li>
<li>Verifies if both the HTTP and WordPress credentials are of the same user (this is the default behavior and can be changed)</li>
<li>Works on all major Web Servers (Tested on Apache, Nginx and Lighttpd)</li>
</ul>
<h4>Plugin Behavior</h4>
<ul>
<li>When this plugin is activated for the first time all WordPress users will have the following Digest credentials<br />
Username: <WordPress username><br />
Password: password<br />
This can be changed from <strong>Users > Your Profile</strong>.</li>
<li>After activating this plugin for the first time you’ll be prompted for HTTP credentials when you logout</li>
<li>Similarly if you change your HTTP username or password you’ll be prompted for this when you logout</li>
</ul>
<h4>Available languages</h4>
<ul>
<li>English</li>
<li>Serbo-Croatian by <a href="http://www.webhostinghub.com/" rel="nofollow ugc">Borisa Djuraskovic</a></li>
</ul>
<p>The <a href="https://websistent.com/wordpress-plugins/http-digest-authentication/" rel="nofollow ugc">HTTP Digest Authentication Plugin</a> official homepage.</p>


HTTP Digest Authentication

Protect your wp-login.php page with HTTP Digest Authentication without the need of adding web server modules or changing config files.

Titan Social Login vs HTTP Digest Authentication