DELETE requests fails due to read-only transaction

[tleefmann]

We are operating a FROST-SERVER with authentication via Keycloak. When sending DELETE Requests for a "Thing" via requests library in python,

url = "https://<our_frost_server>/v1.1/Things(12345)"

payload = {}
headers = {
  'Authorization': 'Bearer <Token>'
}

response = requests.request("DELETE", url, headers=headers, data=payload)

print(response.text)

we are getting the following error message stating:

{ "code": 400, "type": "error", "message": "SQL [delete from \"THINGS\" where \"THINGS\".\"ID\" = ?]; ERROR: cannot execute DELETE in a read-only transaction" }

We have checked so far that:

• the token was generated by a keycloak user with the proper delete-role (otherwise the response code would be 401)
• the postgres is set up with transaction_read_only = off
• that the DELETE command works, when it is directly executed in the postgres DELETE FROM "THINGS" WHERE "ID" = 12345

Could there be another configuration parameter that is preventing DELETE requests via http and results in the respective error message?

[hylkevds]

It does sound like there is something fishy with your connection parameters, or the database configuration.
FROST does not touch the transaction mode of the connection anywhere...

You could try increasing the logging on the database to see if you can find where the transaction is being set to read-only.

[tleefmann]

Thanks @hylkevds, we will check our database configuration again.