# While using DiscourseConnect, is the CONFIRM Account needed?

**URL:** https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963
**Category:** SSO
**Tags:** discourseconnect
**Created:** [November 29, 2023, 12:30pm UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963 "2023-11-29T12:30:01Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![JKBaseer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jkbaseer/32/80471_2.png) [@JKBaseer](https://meta.discourse.org/u/JKBaseer)
#### Post date: [November 29, 2023, 12:30pm UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/1 "2023-11-29T12:30:02Z")

</div>

Hi,  
We have been using [discourse connect](https://meta.discourse.org/t/13045?silent=true) 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.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 29, 2023, 1:17pm UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/2 "2023-11-29T13:17:55Z")

</div>

There’s a parameter that you can pass that tells [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) 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.

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [November 29, 2023, 2:21pm UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/3 "2023-11-29T14:21:48Z")

</div>

Are you setting `require_activation` in the SSO payload?

---

<div class="post-metadata">

### Author: ![JKBaseer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jkbaseer/32/80471_2.png) [@JKBaseer](https://meta.discourse.org/u/JKBaseer)
#### Post date: [November 29, 2023, 2:47pm UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/4 "2023-11-29T14:47:41Z")

</div>

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?

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [November 29, 2023, 3:38pm UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/5 "2023-11-29T15:38:04Z")

</div>

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

---

<div class="post-metadata">

### Author: ![JKBaseer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jkbaseer/32/80471_2.png) [@JKBaseer](https://meta.discourse.org/u/JKBaseer)
#### Post date: [November 30, 2023, 11:54am UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/6 "2023-11-30T11:54:05Z")

</div>

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

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [November 30, 2023, 4:20pm UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/7 "2023-11-30T16:20:03Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![JKBaseer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jkbaseer/32/80471_2.png) [@JKBaseer](https://meta.discourse.org/u/JKBaseer)
#### Post date: [December 6, 2023, 1:23am UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/8 "2023-12-06T01:23:26Z")

</div>

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)

---

<div class="post-metadata">

### Author: ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [December 6, 2023, 2:03am UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/9 "2023-12-06T02:03:44Z")

</div>

From from the rails console, as an example:

```plaintext
User.find_by(username: 'bbaggins').activate!

```

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [January 5, 2024, 2:03am UTC](https://meta.discourse.org/t/while-using-discourseconnect-is-the-confirm-account-needed/286963/10 "2024-01-05T02:03:52Z")

</div>

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