I am trying to delete a user by API following the docs . We use SSO, which seems to make the API require a cookie header coming from SSO authentication. I got past that, and as long as I supply the cookie, other types of actions work fine by GET. But the DELETE results in this “BAD CSRF” error. May…

Are you using an API key for this action? It is required.

Hmmm, where is this at? Did it get resolved?

No, and I really need to get it working. I’ve not tried again since May 19. If there are updates affecting this functionality, should I try again? Thank you very much for the follow-up.

I have tested deleting users through the API on a live hosted site with SSO enabled. I’m using Postman to make the API request. It is deleting users for me. The response is {"deleted": true}. The all_users API key and API username need to be included in the body of the request. One thing I have fou…

BAD CSRF Response When Trying to Delete User by API

Support

ATPJD (Justin Dennis) May 19, 2018, 9:04pm 3

Yes. I’ve tried both the generic one for “system” and my own, as an admin. I have been passing these as GET or POST parameters along with the cookie.

Topic		Replies	Views
SSO and Screened IPs SSO rest-api	8	1884	June 14, 2021
How to delete user accounts via API without IP blocking SSO rest-api	10	423	May 15, 2025
BAD CSRF on user modification Support	2	567	July 6, 2020
Work Around to posting SSO	3	2547	May 18, 2016
I'm getting bad CSRF error even after setting api keys and usernames to my headers General	2	928	April 16, 2022

BAD CSRF Response When Trying to Delete User by API

Related topics