Bug - CSRF token on api request

Forum - Software
1

I’ve updated to 3.25 and now under api/apis/index/SecurityServices, I see edit as an API request. When I try this I always get a CSRF token is missing for other API requests I don’t get this error.

PUT is also missing.

2

Hello,

The index has only GET request.

image
image916×784 31.9 KB

3

I tried:

curl --request PATCH \
  --url https://eramba/api/security-services/edit/23 \
  --header 'Accept: application/json' \
  --header 'Authorization: XXXX' \
  --header 'content-type: application/x-www-form-urlencoded' \
  --data 'name=New Name'

patch/edit didn’t exists under the old api overview, see 3.24.

4

Please try using our Postman collection for this. The headers might need to be slightly different as well.

image
image682×372 41.2 KB

5

postman docu use method put instead of method patch. The view shows edit with method patch. I hoped this will work for single changes as put requires all fields to be defined. (the ui uses this api)

6

Ah yes, I understand the issue now. We need to update the tag in the UI documentation. Currently, only the PUT method is available.

7

Are single value changes planed?

8

No, I’m not aware of that.

9

I would like this feature.