Jacob Schwartz

emfluence interactive marketing

When switching sites using the My Sites links in the admin menu, 
this plugin will automatically authenticate you into the site that you’re going to.
You do already have to be logged into a site in the network; 
this plugin just cuts down on having to log in again due to cookie isolation between domains.
Note: This plugin must be installed on all sites in a network in order to work properly.
Want to change how this plugin works, or add to it? <a href="https://github.com/emfluencekc/multisite-multidomain-single-sign-on" rel="nofollow ugc">Fork it on GitHub</a>!

Multisite Multidomain Single Sign On

Avoid having to separately sign in to separate-domain sites of the same multisite installation!

evansims

Auth0

Josh C

This plugin replaces standard WordPress login forms with one powered by <a href="https://auth0.com" rel="nofollow ugc">Auth0</a> that enables:
<ul>
<li>Universal authentication
<ul>
<li>Over 30 social login providers</li>
<li>Enterprise connections (ADFS, Active Directory / LDAP, SAML, Office 365, Google Apps and more)</li>
<li>Connect your own database</li>
<li>Passwordless connections (using email or SMS)</li>
</ul>
</li>
<li>Ultra secure
<ul>
<li>Multifactor authentication</li>
<li>Password policies</li>
<li>Email validation</li>
<li>Mitigate brute force attacks</li>
</ul>
</li>
</ul>
<h3>Technical Notes</h3>
IMPORTANT: By using this plugin you are delegating the site authentication and profile handling to Auth0. That means that you won’t be using the WordPress database to authenticate users and the default WordPress login forms will be replaced.
Please see our <a href="https://auth0.com/docs/cms/wordpress/how-does-it-work" rel="nofollow ugc">How It Works page</a> for more information on how Auth0 authenticates and manages your users.
<h4>Migrating Existing Users</h4>
Auth0 allows multiple authentication providers. You can have social providers like Facebook, Twitter, Google+, and more, a database of users and passwords (just like WordPress but hosted in Auth0), or you can use an Enterprise directory like Active Directory, LDAP, Office365, Google Apps, or SAML. All those authentication providers might give you an email and a flag indicating whether the email was verified or not. We use that email (only if it is verified) to associate a previous existing user with the one coming from Auth0.
If the email was not verified and there is an account with that email in WordPress, the user will be presented with a page saying that the email was not verified and a link to “Re-send the verification email.” For either scenario, you can choose whether it is mandatory that the user has a verified email or not in the plugin settings.
Please note: In order for a user to log in using Auth0, they will need to sign up via the Auth0 login form (or have an account created for them in Auth0). Once signup is complete, their Auth0 user will be automatically associated with their WordPress user.
<h4>Widget</h4>
You can enable Auth0 as a WordPress widget in order to show it in a sidebar. The widget inherits the main plugin settings but can be overridden with its own settings in the widget form. Note: this form will not display for logged-in users.
<h4>Shortcode</h4>
Also, you can use the Auth0 widget as a shortcode in your editor. Just add the following to use the global settings:
<pre><code>[auth0]
</code></pre>
Like widgets, shortcode login forms will use the settings of the plugin. It can be customized by adding the following attributes:
<ul>
<li><code>icon_url</code> – A direct URL to an image used at the top of the login form</li>
<li><code>form_title</code> – Text to appear at the top of the login form</li>
<li><code>gravatar</code> – Display the user’s Gravatar; set to <code>1</code> for yes</li>
<li><code>redirect_to</code> – A direct URL to use after successful login</li>
<li><code>dict</code> – Valid JSON to override form text (<a href="https://github.com/auth0/lock/blob/master/src/i18n/en.js" rel="nofollow ugc">see options here</a>)</li>
<li><code>extra_conf</code> – Valid JSON to override Lock configuration (<a href="https://auth0.com/docs/libraries/lock/v11/configuration" rel="nofollow ugc">see options here</a>)</li>
<li><code>show_as_modal</code> – Display a button that triggers the login form in a modal; set to <code>1</code> for yes</li>
<li><code>modal_trigger_name</code> – Button text to display when using a modal</li>
</ul>
Example:
<pre><code>[auth0 show_as_modal="1" modal_trigger_name="Login button: This text is configurable!"]
</code></pre>
Note: this form will not display for logged-in users.

Login by Auth0

Does the latest version of plugin use the Lock 10 or Later version of the Lock API?

Please do let me know your inputs about the same.

Thanks

Does updated the plugin used Lock 10 or Later?


Unfortunately, plugin doesn't work and abandoned. On official Github repository you can find this text: 




v4 of the plugin is no longer supported as of June 2023. We are no longer providing new features or bugfixes for that release. Please upgrade to v5 as soon as possible.
OAuth0 Github



But irony that v5 doesn't work as well, so both versions of plugin are just a waste of time


Doesn't work, abandoned

Login by Auth0 provides improved username/password login, Passwordless login, Social login and Single Sign On for all your sites.

Multisite Multidomain Single Sign On vs Login by Auth0