Hi, I created a new user using the REST API. But I am unable to login with the new user credentials. When I search the users table, I cannot find the user account. To troubleshoot the problem, I ran the following CURL cmd. [image] I also tried using a JSON payload with the CURL cmd. I get the same result both times: I cannot login using the new user credentials and the new user is not found in the users table. Any ideas? Thanks

The message here is somewhat misleading; active:false indicates the user was not created but already existed. Check to ensure there isn’t already a user with the same email address, especially if normalize_emails is enabled.

Seems similar to User creation API: ‘active’ attribute set to True but returns False in response [imagem]User creation API: ‘active’ attribute set to True but returns False in response Yes, it seems that the reason for the failure was the flag normalize_email:true it’s true by default. As I turned it off the users got created… However, the API is not considering the normalize_emails flag and is returning success eventhough the user never got created or activated for that matter

I realised that there is an error in our API docs. The active param is only permitted when an API key associated to an admin user is used and has been the case since 2016. For now, I’ve corrected the docs in https://github.com/discourse/discourse/pull/31578

This will help, yeah. It still doesn’t address the original problem of the message being misleading for admins though. ○ → curl -X POST -H "api-key: $API_KEY" -H 'api-username: michael' https://try.discourse.org/users.json --json "$(jo email=michael+test@contoso.com username=michaeltest password=$PASSWORD active=true approved=true)" {"success":true,"active":true,"message":"Your account is activated and ready to use."} ○ → curl -X POST -H "api-key: $API_KEY" -H 'api-username: michael' https://try.discourse.org/users.json --json "$(jo email=michael+test2@contoso.com username=michaeltest2 password=$PASSWORD active=true approved=true)" {"success":true,"active":false,"message":"Your account is activated and ready to use."} ^ only a single user was created above I’m inferring a lot of obfuscation was put into the /users.json path to deter spammers etc. but this seems to be making things difficult for admins as well. I wonder if we should add an explicit admin path to separate the two (normal account creation vs. admin account creation) which will allow the admin function to be unobfuscated.

[imagem] Michael Brown: Check to ensure there isn’t already a user with the same email address, especially if normalize_emails is enabled. You are correct. This was the problem: A user with the same email address already exists. I was searching by username and by created_at desc, which was why the new user didn’t come up in the search results. The successful response threw me off. Thank you for your help.

Criar-Usuário via REST-API, não parece estar funcionando

Suporte ao Produto

RGJ (Richard - Communiteq) 1 Março , 2025 00:08 3

Parece semelhante a User creation API: ‘active’ attribute set to True but returns False in response

Tópico		Respostas	Vistas
User creation via API is a mess! Product Support rest-api	4	178	14 Abril , 2025
User creation API: ‘active’ attribute set to True but returns False in response Product Support rest-api	10	410	1 Janeiro , 2025
Cant create active user via api, Again Product Support	1	572	8 Abril , 2021
Creating and activating users from the API Development	3	1814	21 Setembro , 2020
Disable account confirm emails when creating users via API Development rest-api	26	7206	5 Agosto , 2020

Criar-Usuário via REST-API, não parece estar funcionando

Related topics