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.
Isso está funcionando de alguma forma?
A desativação e a ativação também parecem não funcionar corretamente. Vejo que e-mails ainda estão sendo enviados para usuários pré-ativados.
Tentei enviar chamadas de API definindo active=true e approved=true, mas obtive a seguinte resposta:
{
"success": true,
"active": false,
"message": "Quase lá! Enviamos um e-mail de ativação para '[meu e-mail]'. Siga as instruções no e-mail para ativar sua conta. Se não chegar, verifique sua pasta de spam."
}
No entanto, nenhum e-mail foi enviado e nenhum usuário parece ter sido criado — pelo menos, não vejo nenhum na interface de administração. Qual poderia ser o motivo disso?
Eles podem estar na aba “novo” em vez da aba “ativo”?
Não tenho certeza absoluta sobre o seu caso de uso para criar usuários via API, mas consideraria investigar o uso de Single Sign On.
No entanto, estes são os passos atuais que você precisa seguir para criar um usuário via API sem enviar um e-mail de confirmação. Você precisará fazer 3 requisições:
active=trueOlá Blake, obrigado pela sua resposta!
Não, infelizmente não. Eu verifiquei isso. Por algum motivo, tenho a mesma lista de usuários nas abas “Ativos” e “Novos”, apenas em uma ordem diferente.
Vou migrar de outro lugar (YouTrack, um rastreador de issues) e gostaria de tornar o processo o mais suave e transparente possível para nossos usuários. Portanto, meu plano era migrar todos os usuários via API, depois migrar suas postagens (buscar essas informações no rastreador de issues e criá-las no Discourse via API), comentários e anexos, e só então enviar os convites. É por isso que preciso criar os usuários primeiro — para torná-los autores de suas postagens e comentários.
Sim, li isso neste tópico acima. O problema é que, para a etapa 2, preciso saber o ID do usuário, que deveria estar na resposta da etapa 1, mas não está. Além disso, a mensagem de resposta para “active=true” deveria ser diferente, conforme mostrado aqui: Creating Active Users via the API gem - #36 by mikechristopher