We are using SSO for login and account creation. There’s no other way to login or signing up on our forum. However, the list of screened IPs has dozens of IP addresses which are being added automatically on a daily basis. Is this expected? What makes an IP address get added to the Screened IPs list…

The only way I can think of is when you delete an account and opt for the “delete spammer” button.

Good point — it’s when we remove an account through the API that the IP is being added to the Screened IPs. However, we are issuing the DELETE request using block_ip=false. This is from rails logs: Parameters: {"delete_posts"=>"1", "block_email"=>"0", "blocked_urls"=>"0", "block_ip"=>"0", "id"=>"1…

[imagen] Can't SSO due to blocked IP addresses It sounds like you are calling the “delete as spammer” function, which will automatically blocklist the IP and email address. I think you should revisit that code. You want “plain delete” per the UI, not “delete as spammer”. That could be, althoug…

You may want to use How to reverse engineer the Discourse API and see exactly what requests are sent when you delete a user, and pressing the button that says Delete only [image] … because I can tell you for a fact that if you are seeing IPs get added to the screened list after deletion, you are a…

I had already done that and the deleting API endpoint is the one I have been using, which the same one for both actions (delete only and delete&block) — the only difference is on the parameters that are used with it (block_ip, block_email, …) that I mentioned aboved. [imagen] mentalstring: Howe…

I might have spoken too soon. :disappointed: Having corrected the truthy/falsy parameters to ‘true’/‘false’ strings, I still see entries being added to Screened IPs and Screened Emails upon deleting users. Here’s the rails logs for a API call: Started DELETE "/admin/users/9553.json" for 123.123.1…

As long as you’ve emulated the behavior that you observe when you follow the How to reverse engineer the Discourse API topic, you should be OK. What API calls are you observing in the network monitor when you push the “delete only” button?

In some cases, when the JS isn’t explicitly passing false to the server, the server treats any present value as true. This is likely what you’re encountering here.

SSO y IPs filtradas

Soporte SSO

codinghorror (Jeff Atwood) 14 Junio, 2021 17:53 8

Mientras hayas emulado el comportamiento que observas al seguir el tema Reverse engineer the Discourse API, deberías estar bien. ¿Qué llamadas a la API estás observando en el monitor de red cuando pulsas el botón “solo eliminar”?

1 me gusta

Tema		Respuestas	Vistas
How to delete user accounts via API without IP blocking SSO rest-api	11	288	14 Junio 2025
Can't SSO due to blocked IP addresses SSO rest-api	8	1964	8 Junio 2021
Does SSO make use of Screened IP Addresses to block registrations? SSO	8	901	29 Octubre 2020
BAD CSRF Response When Trying to Delete User by API Support	7	984	5 Marzo 2021
Unable to log into my discourse - "You can't log in as xxx from that IP address." Support	8	3217	28 Mayo 2021

SSO y IPs filtradas

Temas relacionados