hectavex

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.
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!
<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 directly with the trusted third-party login providers.</li>
<li>WP-OAuth collects and stores ONLY the user’s OAuth identity 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 Anyone can register 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>
Visit the <a href="https://github.com/perrybutler/WP-OAuth" rel="nofollow ugc">GitHub development repository</a>.
<h3>History</h3>
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.

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.

InterServer

WordPress Mail.Baby SMTP Plugin (Simple E-Mail Delivery)
if you have problem with your WordPress site not sending emails? Then you got right plugin.
WP Mail.Baby plugin goal is to make email deliverability easy and reliable. We want to ensure your emails reach the inbox.
WP Mail.Baby fixes your email deliverability with various email smtp’s like Mail.baby, SMTP.com, Gmail, SendGrid, Mailgun, Sendinblue and more Api’s.
<h4>What is SMTP?</h4>
SMTP (Simple Mail Transfer Protocol) is an industry standard for sending emails. Proper SMTP configuration helps increase email deliverability by using authentication.
Popular email clients like Gmail, Yahoo, Office 365, and Zoho are in a constant battle with email spammers. One of the things they look at is if an email is originating from the location it claims to be originating from.
If the proper authentication isn’t there, then emails either go in the SPAM folder or worst, don’t get delivered at all.
This is a problem for a lot of WordPress sites because by default, WordPress uses the PHP mail function to send emails generated by WordPress or any contact form plugin like <a href="https://mail.baby/" rel="friend nofollow ugc">Mail.Baby</a>.
The issue is that most WordPress hosting companies don’t have their servers properly configured for sending PHP emails.
The combination of two causes your WordPress emails to not get delivered.
<h4>How does Mail Baby SMTP work?</h4>
Mail.Baby SMTP plugin easily resolves email delivery problems by improving and changing how your WordPress site sends email. We reconfigure the <code>wp_mail()</code> function to either use proper SMTP host credentials or leverage a built-in SMTP mail provider.
When using one of our built-in SMTP mail provider integrations (recommended), emails are sent using the provider’s direct API. This means even if your web host is blocking SMTP ports, your emails still send successfully.
This helps you fix all WordPress not sending email issues.
Mail.Baby SMTP plugin includes many different SMTP setup options:
<ol>
<li>
Mail.Baby (Recommended)
MailBaby is an email smart host that offers outbound filtering. Emails are sent to MailBaby systems, and are analyzed for content.
Email is then routed through an email zone based on the email content, and score of the email, or bounced as spam. IP reputation is handled by MailBaby.
MailBaby monitors all our ips for blacklists, and works with email providers through feedback loops and other abuse monitoring to ensure email delivery.
</li>
<li>
Sendinblue SMTP (Recommended)
</li>
<li>
Mailgun SMTP
</li>
<li>
SendGrid SMTP
</li>
<li>
Gmail SMTP
</li>
<li>
SMTP.com (Recommended)
</li>
</ol>
For most options, you can specify the “from name” and “email address” for outgoing emails.
Instead of having users use different SMTP plugins and workflows for different SMTP providers, we decided to bring it all in one.

Mail Baby SMTP

Send email from your WordPress site using  Mail.baby, SMTP.com, Gmail, SendGrid, Mailgun, Sendinblue and more Api's and Configure wp_mail() with them.

WP-OAuth vs Mail Baby SMTP