While using DiscourseConnect, is the CONFIRM Account needed?

sso
1

Hi,
We have been using discourse connect for sometime. Even though the user creation is authenticated via our internal system, discourse still send the user “CONFIRM YOUR ACCOUNT” email.

Note: The Internal System is already double opt-in.

Questions

  1. Is only users who confirmed the account will receive Digest email?
  2. If yes, is there a way to de-activate that. And the email digest goes to all users who are added in discourse system.
  3. If the first answer is no, I can simply de-activate “CONFIRM YOUR ACCOUNT” email.
1 Like
2

There’s a parameter that you can pass that tells DiscourseConnect that you’ve authenticated the email. I can’t remember what it is, but I think if you look in the docs or spec you should be able to find it.

3

Are you setting require_activation in the SSO payload?

2 Likes
4

Yes the require_activation parameter is being included in the payload. We are sending this as true.

so if we send that as false, Can we de-activate the confirm account email?

2 Likes
5

Yes; setting require_activation to true is telling Discourse that, essentially, the email is unconfirmed and Discourse needs to confirm it itself.

2 Likes
6

One last question, as all previous users who have not confirmed this, can i manually update this users status?

7

Yes - if you run activate! on the User object from the console, it’ll activate them.

Also, you might be able to use the sync_sso endpoint with the right parameters… but I’m not sure about that. Similarly, it might activate them next time they log in if the right parameters are passed.

1 Like
8

Thanks Michael, is there a document you can refer me to identify where I can find the exact things to run on the console? (Like the folder section where this need to run, and the command)

9

From from the rails console, as an example:

User.find_by(username: 'bbaggins').activate!
1 Like
10

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.