Continuing the discussion from Disable Welcome Emails - Can it be done?:
Hello. I’ve tried disabling these in a bunch of ways:
I’ve tried both choices for “discourse narrative bot welcome post type”, and the email sends no matter what.
I’ve also tried doing this:
The email is still being sent. How do I stop it?
Having a similar problem with the “Confirm your new account” email – the PM from discobot is turned off, but users are still receiving the email. It looks like these are different settings. Is there a way to remove the confirmation email?
For clarification, are you adding users via the API @jeffbrowning?
Correct. This is an API call. The data is:
data = {
'api_key': settings.DISCOURSE_API_KEY,
'api_username': settings.DISCOURSE_API_USERNAME,
'name': 'foobar',
'email':email,
'password': password,
'username': 'barbaz',
'active': True,
'approved': True
}
I first tried just sending this API call:
first_res = requests.post('{base}/users.json'.format(base=settings.DISCOURSE_BASE_URL), data
When I did this, my users were not active (despite the active: True in the data above).
I then tried to activate them via the api:
data = {
'api_key': settings.DISCOURSE_API_KEY,
'api_username': settings.DISCOURSE_API_USERNAME,
}
requests.put('{base}/admin/users/{id}/activate'.format(
base=settings.DISCOURSE_BASE_URL,
id=json_response_content['user_id']
), data)
When I did this, the users were active, but the activation email was still being sent. I read here (Creating Active Users via the API gem) That I should try deactivating the user and then activating, so I tried that as well:
data = {
'api_key': settings.DISCOURSE_API_KEY,
'api_username': settings.DISCOURSE_API_USERNAME,
}
requests.put('{base}/admin/users/{id}/deactivate'.format(
base=settings.DISCOURSE_BASE_URL,
id=json_response_content['user_id']
), data)
requests.put('{base}/admin/users/{id}/activate'.format(
base=settings.DISCOURSE_BASE_URL,
id=json_response_content['user_id']
), data)
I could not see any difference in behavior between this code and the previous version (creating the user, and then activating).
Per:
You can now specify that an account is also approved on creation, previously it was beyond cumbersome.
You should use active: 'true' , upper case true will not work.
As long as the API key is associated with an admin you can now create approved, active accounts via the API with no emails.
We will deploy this to our standard tier later this week.
Ok we’ll try that. Do we still need to deactivate + activate or can we take that out as well?
Take that out, but wait till Friday or so to test this out, we have a process prior to pushing our standard tier that we need to follow.
Is there a security risk here? Can we stipulate these cannot be staff (mod/admin) accounts?
It should be fine, we only whitelist staged, approved and active. Admin/moderator is not in the whitelist
I am still having issues creating user accounts using the API. Here are the params I am passing to create the user
$params = array(
'name' => $user_details['name'],
'username' => $user_details['username'],
'email' => $user_details['email'],
'password' => $user_details['password'],
'challenge' => $api_keys->challenge,
'password_confirmation' => $api_keys->value,
'active' => 'true',
'approved' => 'true',
);
The user is being successfully create and no email is being sent. But when I try to login using the account created I am getting the following error message.
You can’t log in yet. We previously sent an activation email to you at *@.org. Please follow the instructions in that email to activate your account. Do I have to change any other settings on the admin? Any help is appreciated.
You might try activating the user with a second API call.
@pfaffman The issue that I am facing with that approach is, a confirmation email gets sent out when I create the user without the “active” parameter. Ideally I would want to create and activate an user using the api without sending the confirmation email.
So my idea was to create the user that way and then try to activate the user via a second API call.
Usually the answer to questions like this are to use SSO, but it’s not clear that it’s what you should do.
Unfortunately we cant use SSO.
The issue with creating an user by passing the active flag and then trying to activate is that we cant activate an already activated user.
I was hoping when active =“true” is passed as a parameter to create the user the user account should be created and activated without sending the confirmation email. Looks like the API request is not doing that.
That sounds like a bug to me.
My next suggestion would be to create it with active. Then deactivate and reactivate with the API. (Or to submit a PR that fixes the bug.)
Yes, Looks like this is the only method that works. Thanks.
Is this working at all?
deactivation and activation also seems not to work properly. I see emails still being sent to pre activated users.
我尝试发送 API 请求并设置 active=true 和 approved=true，但收到以下响应：
{
“success”: true,
“active”: false,
“message”: “您快完成了！我们已向‘[我的邮箱]’发送了一封激活邮件。请按照邮件中的说明激活您的账户。如果未收到，请检查您的垃圾邮件文件夹。”
}
然而，并没有发送邮件，似乎也没有创建用户——至少在管理界面中我看不到任何用户。这可能是什么原因？
它们可能位于“新”标签下，而不是“活动”标签下？
我不太确定您为 API 创建用户的具体使用场景，但建议您考虑使用 单点登录。
不过，以下是通过 API 创建用户且不发送确认邮件所需的当前步骤。您需要发起 3 个请求：
active=true 参数创建用户你好，Blake，感谢你的回复！
不，很遗憾不是。我已经检查过了。不知何故，我在“活跃”和“新”标签下看到的是相同的用户列表，只是顺序不同。
我计划从另一个平台（YouTrack，一个问题跟踪系统）迁移过来，并希望尽可能让迁移过程对我们的用户平滑且无缝。因此，我的计划是：先通过 API 迁移所有用户，然后迁移他们的帖子（从问题跟踪系统获取并通过 API 在 Discourse 中创建）、评论和附件，最后发送邀请。这就是我为什么需要先创建用户——以便让他们成为自己帖子和评论的作者。
是的，我已经在上面的主题中看到了这一点。问题是，对于第 2 步，我需要知道用户 ID，该 ID 本应包含在第 1 步的响应中，但实际上并没有。此外，当设置 active=true 时，响应消息应该有所不同，正如这里所示：Creating Active Users via the API gem - #36 by mikechristopher