hectavex

<p>New providers and features are being added regularly! See the <a href="https://wordpress.org/plugins/wp-oauth/changelog/" rel="ugc">Changelog</a> for details.</p>
<p>As a reminder, WP-OAuth is a still a pre-v1.0 release, which means some features may not work as intended or might change over time. Please report any bugs/issues to the support forum so they can be fixed as soon as possible. Thank you!</p>
<h4>Facts</h4>
<ul>
<li>With so many sites offering membership now, users may suffer registration fatigue and forget their passwords, or use the same password for several sites, increasing their security risk.</li>
<li><a href="http://www1.janrain.com/rs/janrain/images/Industry-Research-Value-of-Social-Login-2013.pdf" rel="nofollow ugc">56% of consumers</a> have at least one major social network profile they could be using for membership, registration and login purposes across multiple websites without having to maintain multiple accounts and passwords (2013).</li>
<li><a href="http://www.marketingprofs.com/charts/2012/7060/social-media-users-prefer-social-login-over-traditional" rel="nofollow ugc">40% of consumers</a> currently utilize social login (2012).</li>
</ul>
<h4>Features</h4>
<ul>
<li>Free, unlimited, unbranded and white-labeled from the beginning. No upselling, no payment plans, no SaaS, no proxy authentication! WP-OAuth communicates from your WordPress site <em>directly</em> with the <em>trusted</em> third-party login providers.</li>
<li>WP-OAuth collects and stores ONLY the user’s <em>OAuth identity</em> in the WordPress database for future logins; no other user information is collected or stored.</li>
<li>Fully integrates with WordPress. Drops into existing WordPress sites and integrates with existing WordPress users.</li>
<li>Supports third-party authentication with Google, Facebook, LinkedIn, Github, Reddit, Windows Live, PayPal and Instagram via OAuth 2.0 / OpenID Connect. Providers can be enabled or disabled.</li>
<li>Automatic user registration if <em>Anyone can register</em> has been enabled under Settings > General > Membership.</li>
<li>Users can manage their third-party login providers via the standard “Your Profile” WordPress page. They may link more providers, or unlink existing providers.</li>
<li>Displays a message via Javascript to the user when they login or logout. This feature can also be disabled.</li>
<li>Add a custom login form to any post or page using the [wpoa_login_form] shortcode. Choose from 4 different layouts. See <a href="https://wordpress.org/plugins/wp-oauth/installation/" rel="ugc">Installation</a> for details.</li>
<li>Customize the default login screen with a logo or background. Point the logo URL to your home page instead of WordPress.org. Hide the default username/password login form if you want. Automatically include login buttons for any providers that are enabled.</li>
<li>Supports cURL or stream context for the authentication flow, meaning the plugin should be compatible with a wide range of PHP servers.</li>
<li>The authentication flow was adapted from code samples provided by Google, Facebook and LinkedIn. It has been updated, rigorously tested and debugged for solid error handling. Provider implementations share much of the same code (very high code re-use) and the differences between the providers have been fully documented.</li>
<li>The user experience and on-boarding process was inspired by StackExchange/StackOverflow login system.</li>
<li>Extremely light-weight, optimized code base for high performance. Doesn’t require third-party OAuth libraries; everything is built first-class into the plugin. Previously, WP-OpenLogin required LightOpenID and Facebook-PHP-SDK, but this is no longer necessary. Keeps the bloat low and the performance high. Tested with P3 Plugin Profiler, WP-OAuth’s plugin overhead is around 0.001 seconds which is 6x less overhead than Akismet in the same run! That means there shouldn’t be a performance hit.</li>
</ul>
<h4>How to Contribute</h4>
<p>Visit the <a href="https://github.com/perrybutler/WP-OAuth" rel="nofollow ugc">GitHub development repository</a>.</p>
<h3>History</h3>
<p>This project is a continuation of <a href="http://github.com/perrybutler/wp-openlogin" rel="nofollow ugc">WP-OpenLogin</a> which was originally developed with OpenID in mind. We’re moving on; OAuth 2.0 is now the standard.</p>


WP-OAuth

Allows users to login or register by authenticating with an existing Google, Facebook, LinkedIn, Github, Reddit (and more!) account via OAuth 2.0.

Noor Alam

<p><a href="https://wphowto.net/gmail-smtp-plugin-for-wordpress-1341" rel="nofollow ugc">Gmail SMTP</a> plugin allows you to authenticate with your Gmail account to send email via Gmail SMTP server.</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/_MCxcvfoGj4?version=3&rel=0&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<p>Most shared hosting servers have restrictions when it comes to email. Usually email will get blocked or missing for no reason. Sometimes it will get blocked when your website reaches the daily limit of outgoing email. This plugin can bypass this issue by routing the email through Gmail’s SMTP server.</p>
<h3>Gmail SMTP Add-ons</h3>
<ul>
<li><a href="https://wphowto.net/how-to-add-a-reply-to-address-in-the-gmail-smtp-wordpress-plugin-6756" rel="nofollow ugc">Reply-To</a></li>
<li><a href="https://wphowto.net/gmail-smtp-plugin-cc-configuration-6770" rel="nofollow ugc">Cc</a></li>
<li><a href="https://wphowto.net/gmail-smtp-email-logger-7336" rel="nofollow ugc">Email Logger</a></li>
</ul>
<h3>Gmail SMTP Benefits</h3>
<ul>
<li>Gmail SMTP plugin is not like most SMTP plugins. It uses the OAuth 2.0 protocol to authorize access to the Gmail API – which means a more secure login system and users won’t have to enter any username or password.</li>
<li>Gmail SMTP plugin uses PHPMailer – a very popular library used for sending email through PHP’s mail function. This libary is also used in the core WordPress to send email.</li>
<li>Gmail SMTP plugin utilizes “wp_mail” (A function used by WordPress to send email) instead of completely overriding it. This way you still get all the benefits of the default mail function. </li>
<li>You no longer need to enable <strong>Allow less secure apps</strong> on your gmail account to fix SMTP connection issue. This issue became prominent from December 2014, when Google started imposing XOAUTH2 authentication (based on OAuth2) to access their apps. This issue still affects almost all the SMTP plugins because they authenticate via username and password.</li>
</ul>
<h3>How OAuth 2.0 Authorization Works</h3>
<ul>
<li>You register an application in the Google Developers Console.</li>
<li>The application is launched and it requests that you give it access to data in your Google account.</li>
<li>If you consent, the application receives credentials to access the Gmail API.</li>
</ul>
<h3>Gmail SMTP Features</h3>
<ul>
<li>Configure your website to send email using Gmail SMTP server</li>
<li>Authenticate using OAuth 2.0 protocol</li>
<li>Authenticate with encryption when sending an email (TLS/SSL)</li>
</ul>
<h3>Gmail SMTP Basic Setup</h3>
<ul>
<li>Create a new project in Google Developers Console.</li>
<li>Enable Gmail API in it.</li>
<li>Create credentials (OAuth client ID) to access this API.</li>
<li>Configure the consent screen for the web application.</li>
<li>Enter a <strong>Product Name</strong> and a <strong>Privacy policy URL</strong>.</li>
<li>Once the consent screen is configured, create a web application.</li>
<li>Go to the plugin settings (<code>Settings->Gmail SMTP</code>).</li>
<li>Set the <strong>Authorized Redirect URL</strong> of the application as the one shown in the settings.</li>
<li>Finish creating the web app.</li>
<li>Copy the newly created <strong>Client ID</strong> and <strong>Client secret</strong> and paste into the settings area.</li>
<li>Enter your OAuth Email, From Email and From name.</li>
<li>Select an encryption.</li>
<li>Enter a port number.</li>
<li>Save the settings.</li>
<li>Now you can authorize your application to access the Gmail API by clicking on the <strong>Grant Permission</strong> button.</li>
<li>Once the application has been authorized Gmail SMTP plugin will be able to take control of all outgoing email.</li>
</ul>
<h3>Gmail SMTP Settings</h3>
<ul>
<li><strong>Authorized Redirect URI</strong>: Authorized redirect URL for your website. You need to copy this URL into your web application.</li>
<li><strong>Client ID</strong>: The client ID of your web application.</li>
<li><strong>Client secret</strong>: The client secret of your web application.</li>
<li><strong>OAuth Email Address</strong>: The email address that you will use for SMTP authentication. This should be the same email used in the Google Developers Console.</li>
<li><strong>From Email Address</strong>: The email address which will be used as the From Address when sending an email.</li>
<li><strong>From Name</strong>: The name which will be used as the From Name when sending an email.</li>
<li><strong>Type of Encryption</strong>: The encryption which will be used when sending an email (TLS/SSL. TLS is recommended).</li>
<li><strong>SMTP Port</strong>: The port which will be used when sending an email. If you choose TLS it should be set to 587. For SSL use port 465 instead.</li>
<li><strong>Disable SSL Certificate Verification</strong>: As of PHP 5.6 a warning/error will be displayed if the SSL certificate on the server is not properly configured. You can check this option to disable that default behaviour.</li>
</ul>
<h3>Gmail SMTP Test Email</h3>
<p>Once you have configured the settings you can send a test email to check the functionality of the plugin.</p>
<ul>
<li><strong>To</strong>: Email address of the recipient.</li>
<li><strong>Subject</strong>: Subject of the email.</li>
<li><strong>Message</strong>: Email body.</li>
</ul>
<p>For detailed setup instructions please visit the <a href="https://wphowto.net/gmail-smtp-plugin-for-wordpress-1341" rel="nofollow ugc">Gmail SMTP</a> plugin page.</p>


Gmail SMTP


Only the necessary settings, simple and clean, good description. Thanks!


All is good!


The plugin is great when it works.



The plugin suddenly stopped working. I contacted support, they checked the site, and stopped answering. They did not say yes, no, we can or cannot fix it. They stopped answering.My finding are that the plugin only works on small wordpress website installs, on the root directory.



The plugin is not capable to handle large sites or sites installed on directories other than the root.That means, if you grow, you will start encountering problems with this plugin. Same as I did.



I am now using Fluent SMTP, it works out of the box with no sweat.



Thanks 


Good when it works, only for small sites installed at root

Connect to Gmail SMTP server to automatically send email from your WordPress site. Configure wp_mail() to use SMTP with OAuth 2.0 authentication.

WP-OAuth vs Gmail SMTP