How to Deactivate the Discourse Activation Email


(Ryan Collins) #1

Hi team,

Is it possible to deactivate the requirement to verify emails with discourse?

I am using Discourse with my Wordpress website connected via SSO.

In my situation, it just doesn’t make sense for users to be required to verify their email.

Just curious.

Thanks!


Does a social login WP plugin address Discourse expectation for email verification? (with WP as SSO provider)
(Simon Cossar) #3

Unless the default WordPress New User Notification email is sent as a part of your WordPress registration process, the plugin sets the SSO parameter require_activation to true. There is a hook that you can use to bypass this. The hook is called discourse_email_verification. It passes two parameters:

  • $require_activation - whether or not the email address has been validated by WordPress
  • $user - the WordPress user object

If you want to disable email validation for all users, then you don’t need to use the parameters. You can add something like this to your theme’s functions.php file or a plugin:

Note: don’t use this unless you know that your user’s email addresses are valid.

add_filter( 'discourse_email_verification', 'wpdc_custom_disable_email_verification' );
function wpdc_custom_disable_email_verification() {

    return false;
}

Auto-activate new users
(Ryan Collins) #4

Thank you Simon!

I will get to work on this and let you know if I have any questions. I really appreciate the reply.


(Banker) #5

Hello, how would I go about adding this code into my discourse forum?


(Simon Cossar) #6

Before you add the code, you need to be sure that email addresses are being verified when users create an account on your WordPress site. If you are sure that emails are being verified, then all you need to do is copy the above code into your theme’s functions.php file.

If you are not sure about this, it’s best to either leave things as they are, or to use the default WordPress login system. If you use the default WordPress login system, the WP Discourse plugin will recognize that user’s email addresses are verified and will not require an activation email to be sent when users first login to Discourse.


(Banker) #7

I am using SSO through wordpress as well as the wordpress login. However, once a user logs in for the first time, discourse requires them to approve their email when they try and access the forum part of the site. I’ve looked around but can’t find a solution besides removing the email verification altogether.


(Simon Cossar) #8

By ‘default WordPress login’ I mean that users are creating an account on a page that looks like this:

If this is the registration process you are using, then users should not be having to verify their email address before first logging into Discourse.

There are quite a few front-end registration plugins for WordPress that will create an account and automatically login a user without requiring the user to verify their email address. Woocommerce is an example of a plugin that does this. This can be a security risk for Discourse.


(Banker) #9

I understand. I think then I am not using the wordpress login. I am using Memberpress to run an membership site and the registration is through there.


(Rick) #10

@Simon_Cossar I will be trying this solution soon. But I am also having a problem with 2FA and SSO.

Do you know if there I a way to make all this work with 2FA (2-factor authentication)?

I have 2FA enable for administrators only, but it creates a loop and admins cannot log in to wp-admin. For all other users, it works fine (but I don’t have 2FA for other users, only admins).

When I disable 2FA for the admins then they can sign in to back-end no problem.
The 2FA is being implemented through iThemes security.

Do you know if there is a way to fix this issue? I want to leave 2FA for all admins because they have access to back end.

And just for a peace of mind, I want to mention that the only reason I am doing this is because I have SSO activated through Wordpress and Wordpress is doing the email verification in addition to that. In addition, I also disabled public registrations meaning that the only way to create an account is through Wordpress.

the setting is by invite only . See below:

:arrow_down:


(Simon Cossar) #11

Having extra security for admins could be a good idea. There have been issues reported previously about conflicts between the iThemes Security plugin and WP DIscourse SSO. I’d like to try it out to see if it can be made to work. I’ll let you know what I find.

On the Discourse end, all you need to do is select the ‘enable sso’ Site Setting. When that setting is enabled, Discourse only allows accounts to be created through SSO.


(Rick) #13

Thank you so much @Simon_Cossar for splitting the topic to keep each issue separated.

When it comes to this:

  1. I see you mentioned “that it could be good idea”…

Is this not standard practice in the Wordpress world?

I just ask because I may just simply be over killing it in the security aspect. I am truly not sure if that is standard practice. I am use to 2FA everything in my path since my previous job was security analyst for digital fraud operations at one of the largest banks in the US so I just want to protect as much as possible. But it may be that I just have security paranoia and need to ease up a bit :wink:. I still have 2 different offsite backups and other security settings through iThemes.

  1. for this:

Thanks so much! I appreciate you taking the extra time to look into this. Please do let me know, I am interested in seeing what you find out.

  1. Finally for this:

I will recheck my settings to go with your suggestions.

Thanks so much for all your help. This community is truly a lifesaver!


(Simon Cossar) #14

Having 2FA for admins is a good idea. I’ll do some tests with the Google Authenticator app later this week.


(Simon Cossar) #15

I have tested this with the MiniOrange Google Authenticator plugin. I’m not having any trouble with SSO login when I have to enter an authentication code before logging into WordPress. It could be that there is an issue specific to the iThemes Security plugin. I’d like to test that out, but the plugin requires an signing up for a yearly subscription.

I’ll test this with any up to date security plugins that can be installed free of charge.